On 7/4/2016 10:18 AM, Lorenzo Fundaró wrote: > when deploying solr (in solrcloud mode) in the cloud one has to take > care of storage, and as far as I understand it can be a problem > because the storage should go wherever the node is created. If we have > for example, a node on EC2 with its own persistent disk, this node > happens to be the leader and at some point crashes but couldn't make > the replication of the data that has in the transaction log, how do we > do in that case ? Ideally the new node must use the leftover data that > the death node left, but this is a bit cumbersome in my opinion. What > are the best practices for this ?
I can't make any sense of this. What is the *exact* problem you need to solve? The details can be very important. We might be dealing with this: http://people.apache.org/~hossman/#xyproblem Thanks, Shawn
