Re: Failure to load shards

2017-06-13 Thread Erick Erickson
John: The patch certainly doesn't apply cleanly to 5.4. that said, there were just a few conflicts so that part doesn't look too bad. I don't know anyone who has actually backported it that far so it's unexplored territory. Note that the patch was generated for 6x which requires Java 1.8 whereas

Re: Failure to load shards

2017-06-13 Thread John Bickerstaff
Eric, We're using Solr 5.5.4 and aren't really eager to change at this moment... Off the top of your head - what probability that the patch here: https://issues.apache.org/jira/browse/SOLR-10524 ... will work in 5.5.4 with minimal difficulty? For example, were there other classes introduced in

Re: Failure to load shards

2017-06-09 Thread John Bickerstaff
Thanks Eric! It's very likely that the auto scale groups spinning up new Solrs hit zookeeper harder than our initial deploy... Just due to the way things get staggered during the deploy. Unfortunately, I don't think there's a way to stagger the auto scale group's work of bringing up Solr boxes (

Re: Failure to load shards

2017-06-09 Thread Erick Erickson
John: First place I'd look is the ZooKeeper Overseer queue. Prior to 6.6 there were some inefficiencies in how those messages were processed and that queue would get very, very large when lots of replicas came up all at once, and that would gum up the works. See: SOLR-10524. The quick check would