We are running in an orchestration environment — either Mesos/Chronos/Marathon or Kubernetes.
Each docker container needs to join the Jackrabbit cluster for the lifetime of that container and then leave the Jackrabbit cluster when its work is complete. When each container joins the Jackrabbit cluster it is assigned a unique cluster node id (repository.xml). We also have no upper bound on the number of our containers that may join the cluster at any given time. Will this “dynamic” clustering work or will we encounter issues? Is this ill-advised? or are there things we need to do beyond uniquely identify each cluster node. I Am trying to get ahead of issues that may arise when exercising this. Any thoughts at all would be appreciated. Thanks, -John
