Interestingly, If I simply add one document to the full cluster after all 6 nodes are active, this entire problem goes away. This appears to be because a transaction log entry is created which in turn prevents the new nodes from going into full replication recovery upon leader change.
Adding a document is a hacky solution, however. It seems like new nodes that were added via ADDREPLICA should know more about versions than they currently do. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Cloud-A-B-Deployment-Issue-tp4302810p4302949.html Sent from the Solr - User mailing list archive at Nabble.com.
