We have been working on some changes that should help with this.. 1st challenge is having the node name remain static regardless of where the node runs (right now it uses host and port, so this won't work unless you are using some sort of tunneled or dynamic networking).. We have a patch we are working on for this.. Once this is in place and you use the "zookeeper is truth" mode for solr cloud and this should seamlessly transition into the new node (and replicate).. Will update with the ticket number as I forget it off hand
Steve On Mon, Jul 4, 2016 at 9:47 AM Lorenzo Fundaró < lorenzo.fund...@dawandamail.com> wrote: > Hello guys, > > I am trying to run Solr on my infrastructure using docker containers and > Mesos. My problem is that I don't have a shared filesystem. I have a > cluster of 3 shards and 3 replicas (9 nodes in total) so if I distribute > well my nodes I always have 2 fallbacks of my data for every shard. Every > solr node will store the index in its internal docker filesystem. My > problem is that if I want to relocate a certain node (maybe an automatic > relocation because of a hardware failure), I need to create the core > manually in the new node because it's expecting to find the core.properties > file in the data folder and of course it won't because the storage is > ephemeral. Is there a way to make a new node join the cluster with no > manual intervention ? > > Thanks in advance ! > > > -- > > -- > 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, Niels Nüssler und Michael Pütz > AG Charlottenburg HRB 104695 B http://www.dawanda.com >
