I have a zookeeper quorum on ec2 instances. Just w...
# getting-started
r
I have a zookeeper quorum on ec2 instances. Just wanted to check if i can provide the zookeeper quorum addresses as a comma seperated values for controller.zk.str and similar params for broker and server? Just wanted to try this out on EC2 instances instead of EKS.
Want to confirm before i provision instances. TIA
x
if eks nodes can resolve the dns then it’s possible, you can quickly check it by enter into a k8s container
r
I am not using eks since I dont have much experience in K8s. I am having multiple ec2 instances for each of the components (servers, brokers and coordinators). Just wanted to know if i can pass the ZK quorum addresses as a param when I start the other components @Xiang Fu
x
then it’s totally fine
just you need to configure zk as the comma separated list
🙂 1
👍 1
r
Might sound trivial, but the broker and server configs doesn’t have a parameter for passing zookeeper info like the controller? But I can see in the documentation that we can pass zkAddress as a CLI argument. https://docs.pinot.apache.org/configuration-reference/broker https://docs.pinot.apache.org/configuration-reference/server
m
You can use the same config as for the controller (
controller.zk.str
) or you could use
pinot.zk.server
both will get picked up on startup
r
Oh okay. Was expecting something similar but got confused since it wasnt listed on the docs. Let me try it that way. Thanks
Quick question, in case I add a new instance to the cluster ( maybe a new server) does the cluster automatically rebalance the segments?
x
no auto rebalance, you need to call controller api to rebalance the table explicitly
r
@Xiang Fu even in the case of kinesis data stream(on demand) ingestion?
x
yes
new segment assignment will take into account of the new added servers
r
There is a different thread which has a different answer.
x
but not moving old data to that server
oh?
if a consuming segment is closed and you get a new segment, then it could be assigned to new server
r
Oh okay. So the new data will move into the new server without rebalancing but for old data to move into new server requires rebalancing?
x
rebalance is for redistribute old data
r
Got it.