Hi Shawn. Actually what im trying to find out is whether this is the best approach for deploying solr in the cloud. I believe solrcloud solves a lot of problems in terms of High Availability but when it comes to storage there seems to be a limitation that can be workaround of course but it's a bit cumbersome and i was wondering if there is a better option for this or if im missing something with the way I'm doing it. I wonder if there are some proved experience about how to solve the storage problem when deploying in the cloud. Any advise or point to some enlightening documentation will be appreciated. Thanks. On Jul 4, 2016 18:27, "Shawn Heisey" <apa...@elyograg.org> wrote:
> 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 > >
