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 its core, then synchronize and finally serve again,
Please confirm. Regards Lars On Thu, 6 Jul 2017 at 23:18, Erick Erickson <erickerick...@gmail.com> wrote: > 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 > <lars.karlsson.st...@gmail.com> wrote: > > Hi all, please help clarify how solr will handle network segmented > replica > > meanwhile configuration and reload of cores/nodes for one collection is > > applied? > > > > Does the replica become part of the collection after connectivity is > > restored? > > > > Hence the node is not down, but lost ability to communicate to zookeepers > > and other nodes for a short while. > > > > Regards > > Lars >
