Anyone that might be able to test this, or already did, please help
clarify..
On Fri, 7 Jul 2017 at 00:42, Dave wrote:
> Sorry that should have read have not tested in solr cloud.
>
> > On Jul 6, 2017, at 6:37 PM, Dave wrote:
> >
> > I have tested that out in solr cloud, but for solr master sla
Sorry that should have read have not tested in solr cloud.
> On Jul 6, 2017, at 6:37 PM, Dave wrote:
>
> I have tested that out in solr cloud, but for solr master slave replication
> the config sets will not go without a reload, even if specified in the in the
> slave settings.
>
>> On Jul
I have tested that out in solr cloud, but for solr master slave replication the
config sets will not go without a reload, even if specified in the in the slave
settings.
> On Jul 6, 2017, at 5:56 PM, Erick Erickson wrote:
>
> I'm not entirely sure what happens if the sequence is
> 1> node dro
I'm not entirely sure what happens if the sequence is
1> node drops out due to network glitch but Solr is still running
2> you upload a new configset
3> the network glitch repairs itself
4> the Solr instance reconnects.
Certainly if the Solr node is _restarted_ or _reloaded_ the new
configs are re
Ok, so although there was a configuration change and/or schema change
(during network segmentation) that normally requires a manual core reload
(that nowadays happen automatically via the schema API), this replica will
get instructions from Zookeeper to update its configuration and schema,
reload i
right, when the node connects again to Zookeeper, it will also rejoin
the collection. At that point it's index is synchronized with the
leader and when it goes "active", then it should again start serving
queries.
Best,
Erick
On Thu, Jul 6, 2017 at 2:04 PM, Lars Karlsson
wrote:
> Hi all, please
