- What kind of discovery mechanism do you use? I don't know - whichever is the default discovery mechanism when running org.apache.sling.launchpad-8-webapp.war on Tomcat 8 and I've modified the content of the war file so that it will start with run modes oak|oak_mongo, so that by default it's looking for mongo on localhost.
- Are the Sling/Oak instances and MongoDB clocks in sync? I didn't realize this is important, but they must be as it's all in my local machine. I'm not even using vagrant or virtual machines - just a buncha stuff on local MacOS. - Do you have anything suspicious in the error logs when the instances shut themselves down? See my reply above. Nothing very indicative, just the instance declaring that the clusterview has changed and itself is no longer in it... - What happens if after the instances are shut down and a new leader is elected you restart one of the old instances? Then they boot out the other other guy. They just take turns booting each other out. To be specific, I had a sling instance on :8080 and another on :8081, and they were connected to mongo localhost. Everything worked great as I developed on them for a good 6 hours. Then I added and instance on :8082 and when it connected to mongo localhost, tomcat 8080 and 8081 both shut down, and the log file is just their mutual agreement that the new clusterview doesn't include them. I immediately started 8080 and 8081 back up again, and the same thing happened but in reverse, with 8082 shutting itself down. -- View this message in context: http://apache-sling.73963.n3.nabble.com/Join-new-member-to-Sling-Oak-cluster-tp4069454p4069493.html Sent from the Sling - Users mailing list archive at Nabble.com.
