Hi guys. Thank you for your answers. @Upayavira I'm interested on your presentation. @steven im also interested on this patch you're working on.
I actuallly believe that a solution is can be something like a supervisor or sidekick that knows when the containers die and provisions the new ones with the right core configuration. This will have to make the corresponding api calls to solr of course. Any github project where i can take a look to the Progress you are making? Thanks On Jul 5, 2016 01:27, "Steven Bower" <sbo...@alcyon.net> wrote: I don't think that's a bad approach with the sidecar.. We run a huge number of solr ~5k instances so adding sidecars for each one ads a lot of extra containers.. What I mean by transition is a container dying and a new one being brought online to replace it.. With the mod we are working on you won't need the sidecar to add cores to the new node via the API and remove the old cores.. A new instance would start up with the same node name and just take over the existing cores (of course will require replication but that will happen automatically ) Steve On Mon, Jul 4, 2016 at 5:27 PM Upayavira <u...@odoko.co.uk> wrote: > What do you mean by a "transition"? > > Can you configure a sidekick container within your orchestrator? Have a > sidekick always run alongside your SolrCloud nodes? In which case, this > would be an app that does the calling of the API for you. > > Upayavira > > On Mon, 4 Jul 2016, at 08:53 PM, Steven Bower wrote: > > My main issue is having to make any solr collection api calls during a > > transition.. It makes integrating with orchestration engines way more > > complex.. > > On Mon, Jul 4, 2016 at 3:40 PM Upayavira <u...@odoko.co.uk> wrote: > > > > > Are you using Solrcloud? With Solrcloud this stuff is easy. You just > add > > > a new replica for a collection, and the data is added to the new host. > > > > > > I'm working on a demo that will show this all working within Docker and > > > Rancher. I've got some code (which I will open source) that handles > > > config uploads, collection creation, etc. You can add a replica by > > > running a container on the same node as you want the replica to reside, > > > it'll do the rest for you. > > > > > > I've got the Solr bit more or less done, I'm now working on everything > > > else (Dockerised Docker Registry/Jenkins, AWS infra build, etc). > > > > > > Let me know if this is interesting to you. If so, I'll post it here > when > > > I'm done with it. > > > > > > Upayavira > > > > > > On Mon, 4 Jul 2016, at 02:46 PM, Lorenzo Fundaró 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 > > > >
