Incorrect cfg for clustering?

[sleighzy]

Incorrect cfg for clustering?

[sleighzy]

Hi @ken-tune .

Presumably based on your usage of kafka_tag you're using AWS and dynamic inventory. What script/tooling are you using for this?

At first glance it looks like maybe you're defining this at the playbook level so it may not be evaluated per host, as opposed to using it in the host vars...? For example, if this evaluates to 1 initially and is then passed to the role as the default value then due to there not being an individual zookeeper_id on each host then it will fall back on the default. See https://github.com/sleighzy/ansible-zookeeper/blob/master/templates/zoo.cfg.j2#L48

server.{{ hostvars[host].zookeeper_id | default(zookeeper_id) }}.............

Presumably the /var/lib/zookeeper/myid file on all your nodes contain this same 1 value as well?

I don't know how you currently tag your EC2 instances but you could specify this value on a tag there, e.g. named zookeeper_id, and then use that in the host vars although I don't know how much additional overhead this adds for you.

I'll need to set aside some time to test similar config to yours locally to see if I can replicate and provide something more helpful.

[ken-tune]

Hi @sleighzy

If it helps, what's seen on the other two hosts is

server.2=ip-10-0-0-65.ec2.internal:2888:3888
server.2=ip-10-0-1-234.ec2.internal:2888:3888
server.2=ip-10-0-2-207.ec2.internal:2888:3888

&

server.3=ip-10-0-0-65.ec2.internal:2888:3888
server.3=ip-10-0-1-234.ec2.internal:2888:3888
server.3=ip-10-0-2-207.ec2.internal:2888:3888

with the content of /var/lib/zookeeper/myid matching the X in server.X in each case. So zookeeper_id is being evaluated at the host level.

I can figure out a workaround ( run a subsequent process to correct) so maybe will just leave this with you and if I have some free cycles will figure out a patch if you don't beat me to it.