Closed rmarting closed 11 months ago
@gbaufake Could you double check it? I think it is needed to review the implementation of the zookeeper id to avoid this kind of issue.
It was something that we missed to review in the #99 implementation. :see_no_evil:
We need to update the following:
List of servers which should be members of the Zookeeper cluster.
server.1=f38mw01:2888:3888:participant;f38mw01:2181
server.2=f38mw02:2888:3888:participant;f38mw02:2181
server.3=f38mw03:2888:3888:participant;f38mw03:2181
to match the ids when defined.
These lines need to be modified.
SUMMARY
The new feature of identify the zookeeper id works if you use a sequence of ids starting from 0, but if you use a difference sequence, then zookeeper does not start and fails with the following exception:
This is because the list of servers of the zookeeper cluster has not the same id (based in the zookeeper group index). This is the list created, not linked with the id declared in the
myid
file:This also affects authorization provider if authentication is enabled:
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
Current content of the
main
branchSTEPS TO REPRODUCE
The following inventory will fails with this issue as the ids are not declared sequentialy
This can happen with any playbook installing multiple zookeepers.
EXPECTED RESULTS
Use the zookeeper id per host in the list of servers of the ensemble (including the autorization providers).
ACTUAL RESULTS