On 5 July 2016 at 15:55, Shawn Heisey <apa...@elyograg.org> wrote: > On 7/5/2016 1:19 AM, Lorenzo Fundaró wrote: > > 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. > > When you ask whether "this is the best approach" ... you need to define > what "this" is. You mention a "storage problem" that needs solving ... > but haven't actually described that problem in a way that I can > understand.
So, Im trying to put Solrcloud in a cloud provider where a node can disappear any time because of hardware failure. In order to preserve any non replicated updates I need to make the storage of that dead node go to the newly spawned node. I am not having a problem with this approach actually, I just want to know if there is a better way of doing this. I know there is HDFS support that makes all this easier but this is not an option for me. Thank you and I apologise for the unclear mails. > > Let's back up and cover some basics: > > What steps are you taking? What do you expect (or want) to happen? What actually happens? > > The answers to these questions need to be very detailed. > > Thanks, > Shawn > > -- -- Lorenzo Fundaro Backend Engineer E-Mail: lorenzo.fund...@dawandamail.com Fax + 49 - (0)30 - 25 76 08 52 Tel + 49 - (0)179 - 51 10 982 DaWanda GmbH Windscheidstraße 18 10627 Berlin Geschäftsführer: Claudia Helming und Niels Nüssler AG Charlottenburg HRB 104695 B http://www.dawanda.com
