Apache Pinot Docs
Search…
latest
For Users
For Developers
For Operators
Configuration Reference
Decoupling Controller from the Data Path
For Real Time Pinot tables
Ingestion bottleneck on the Pinot Controller
In case of RealTime Pinot tables, whenever a Pinot server finishes consuming a segment, it goes through a segment completion protocol sequence. The default approach is to upload this segment to the lead Pinot controller which in turn will persist it in the segment store (eg: NFS, S3 or HDFS). As a result, since all the realtime segments flow through the controller, it can become a bottleneck and slow down the overall ingestion rate. To overcome this limitation, we've added a new policy which allows bypassing the controller in the segment completion protocol. This is internally named as "Peer Download policy".
Overview of Peer Download policy
When this is enabled, the Pinot servers will attempt to upload the completed segment to the segment store directly, thus by-passing the controller. Once this is finished, it will update the controller with the corresponding segment metadata. The reason this policy is named
peer download is because if the segment store is unavailable for whatever reason, the corresponding segments can still be downloaded directly from the Pinot servers.Please Note: This is available in the latest master (not in 0.5.0 release)
How to enable Peer Download for Segments
This scheme only works for real-time tables using the Low Level Consumer (LLC) mode. The changes needed are as follows:
Controller Config
Add the following things to the Controller Config
1
controller.allow.hlc.tables=false
2
controller.enable.split.commit=true
Copied!
Server Config
Add the following things to the server config
1
pinot.server.instance.segment.store.uri=<URI of segment store>
2
pinot.server.instance.enable.split.commit=true
3
pinot.server.storage.factory.class.(scheme)=<the corresponding Pinot FS impl>
Copied!
Here URI of segment store should point to the desired full path in the corresponding segment store with both filesystem scheme and path (eg:
file://dir or hdfs://path or s3://path)Replace the last field (i.e., scheme) of pinot.server.storage.factory.class.(scheme) with the corresponding scheme (e.g., hdfs, s3 or gcs) of the segment store URI configured above. Then put the PinotFS subclass for the scheme as the config value.
Table config
1
"segmentsConfig": {
2
...
3
"peerSegmentDownloadScheme": "http"
4
}
Copied!
In this case, the
peerSegmentDownloadScheme can be either http or https.Config for failure case handling
Enabling peer download may incur LLC segments failed to be uploaded to segment store in some failure cases, e.g. segment store is unavailable during segment completion. Add the following controller config to enable the upload retry by a controller periodic job asynchronously.
1
controller.realtime.segment.deepStoreUploadRetryEnabled=true
Copied!
Last modified 4mo ago