On 8/2/2017 8:56 AM, Michael B. Klein wrote:
> SCALE DOWN
> 1) Call admin/collections?action=BACKUP for each collection to a
> shared NFS volume
> 2) Shut down all the nodes
>
> SCALE UP
> 1) Spin up 2 Zookeeper nodes and wait for them to stabilize
> 2) Spin up 3 Solr nodes and wait for them to sho
And the one that isn't getting the updates is the one marked in the cloud
diagram as the leader.
/me bangs head on desk
On Wed, Aug 2, 2017 at 10:31 AM, Michael B. Klein wrote:
> Another observation: After bringing the cluster back up just now, the
> "1-in-3 nodes don't get the updates" issue p
Another observation: After bringing the cluster back up just now, the
"1-in-3 nodes don't get the updates" issue persists, even with the cloud
diagram showing 3 nodes, all green.
On Wed, Aug 2, 2017 at 9:56 AM, Michael B. Klein wrote:
> Thanks for your responses, Shawn and Erick.
>
> Some clarif
Thanks for your responses, Shawn and Erick.
Some clarification questions, but first a description of my (non-standard)
use case:
My Zookeeper/SolrCloud cluster is running on Amazon AWS. Things are working
well so far on the production cluster (knock wood); its the staging cluster
that's giving me
And please do not use optimize unless your index is
totally static. I only recommend it when the pattern is
to update the index periodically, like every day or
something and not update any docs in between times.
Implied in Shawn's e-mail was that you should undo
anything you've done in terms of co
On 8/1/2017 12:09 PM, Michael B. Klein wrote:
> I have a 3-node solrcloud cluster orchestrated by zookeeper. Most stuff
> seems to be working OK, except that one of the nodes never seems to get its
> replica updated.
>
> Queries take place through a non-caching, round-robin load balancer. The
> col
