only ever one marathon event subscriber? about docker-mongodb-marathon HOT 4 CLOSED

You're correct, and this was initially intended as-is. This project is not yet production-ready, because auth features are not yet implemented. Please keep that in mind.

I added a new functionality so that all node start to listen to Marathon events once the cluster was initialized. The secondary node will safely ignore the updates, until the master crashes and a secondary is elected a the new master.

from docker-mongodb-marathon.

The images have been built on the Docker Hub. Please check and close the issue if it's resolved.

from docker-mongodb-marathon.

I think a better solution is to just subscribe every instance to marathon,
and set ready=true unless its the initial node. Thats what I've done anyway. seems to work fine.

from docker-mongodb-marathon.

Why would this be a better solution? I think it's correct to wait until the cluster setup is finished.

Anyway, I'll keep it the way it is now.

from docker-mongodb-marathon.