Controller

The Pinot Controller is responsible for a number of things
Controllers maintain the global metadata (e.g. configs and schemas) of the system with the help of Zookeeper which is used as the  persistent metadata store.
Controllers host Helix Controller and is responsible for managing other pinot components (brokers, servers, minions) 
They maintain the mapping of which servers are responsible for which segments. This mapping is used by the servers, to download the portion of the segments that they are responsible for. This mapping is also used by the broker to decide which servers to route the queries to.
Controller has admin endpoints for viewing, creating, updating and deleting configs which help us manage and operate the cluster.
Controllers also have endpoints for segment uploads which are used in offline data pushes. They are responsible for initializing realtime consumption and coordination of persisting the realtime segments into the segment store periodically.
They undertake other management activities such as managing retention of segments, validations.
There can be multiple instances of Pinot controller for redundancy. If there are multiple controllers, Pinot expects that all of them are configured with the same back-end storage system so that they have a common view of the segments (e.g. NFS). Pinot can use other storage systems such as HDFS or ADLS.
Starting a Controller
Make sure you've setup Zookeeper. If you're using docker, make sure to pull the pinot docker image.  To start a controller 
Docker Image
Launcher Scripts
1
docker run \
2
    --network=pinot-demo \
3
    --name pinot-controller \
4
    -p 9000:9000 \
5
    -d ${PINOT_IMAGE} StartController \
6
    -zkAddress pinot-zookeeper:2181
Copied!
1
bin/pinot-admin.sh StartController \
2
  -zkAddress localhost:2181 \
3
  -clusterName PinotCluster \
4
  -controllerPort 9000
Copied!

Cluster

Broker

Last modified 1yr ago

Copy link

Contents

Starting a Controller