hi Shawn,
as I replied to Markus, of course I know (and use) the collections api to
reload the config. I am asking what would happen in that scenario:
- config updated (but collection not reloaded)
- i restart one node
now one node has the new config and the rest the old one??
To which he alrea
On 2/9/2017 5:24 AM, xavier jmlucjav wrote:
> I always wondered, if this was not really needed, and I could just call
> 'restart' in every node, in a quick loop, and forget about it. Does anyone
> know if this is the case?
>
> My doubt is in regards to changing some config, and then doing the above
Hello - see inline.
-Original message-
> From:xavier jmlucjav
> Sent: Thursday 9th February 2017 13:46
> To: solr-user
> Subject: Re: procedure to restart solrcloud, and config/collection consistency
>
> Hi Markus,
>
> yes, of course I know (and use) the colle
t;
> -Original message-
> > From:xavier jmlucjav
> > Sent: Thursday 9th February 2017 13:24
> > To: solr-user
> > Subject: procedure to restart solrcloud, and config/collection
> consistency
> >
> > Hi,
> >
> > When I need to restart
, i'd really recommend using
these tools.
Markus
-Original message-
> From:xavier jmlucjav
> Sent: Thursday 9th February 2017 13:24
> To: solr-user
> Subject: procedure to restart solrcloud, and config/collection consistency
>
> Hi,
>
> When I need to res
Hi,
When I need to restart a Solrcloud cluster, I always do this:
- log in into host nb1, stop solr
- log in into host nb2, stop solr
-...
- log in into host nbX, stop solr
- verify all hosts did stop
- in host nb1, start solr
- in host nb12, start solr
-...
I always wondered, if this was not rea
