On 3/25/2022 9:49 PM, Phil Budne wrote:
Thanks for the pictures. I think I may have it figured out.The Dockerfile for zookeeper runs upconf and linkconf for each collection, and then saves a copy of /var/lib/zookeeper duing construction of the image, and doesn't persist any changes made while running. I found this comment: # Move the "clean" ZooKeeper data directory to /var/lib/zookeeper-template/ # so that we could use a clean data directory (e.g. without Solr hostnames # hardcoded) on every ZooKeeper start.
So when there is a restart they basically wipe the ZK database to a "clean" state? That seems like fixing an improperly placed nail for hanging a painting by bulldozing and rebuilding the entire house. Sure, it will work, but it's silly.
So can I preload the aliases data, perhaps with the zkcli "putfile" command?
That should work. Or maybe you could figure out how to build that into the ZK template.
As a workaround to the "problem" they are trying to solve ... each Solr node can be configured to send a different string for its hostname to zookeeper than its actual hostname. Then you just make sure DNS is always up to date and uses a low TTL value for the docker-related names.
Thanks, Shawn
