Please raise a JIRA for this, I can see why this would occur. You can manually change the clusterstate.json file when this happens as a stop-gap, I'd have all the Solr instances down when doing this though.
Best, Erick On Tue, Jun 23, 2015 at 8:19 AM, Arnon Yogev <arn...@il.ibm.com> wrote: > We have a use case where documents are indexed in shards according to a > specific field (shard per user), and the number of shards is unknown when > creating the collection. > For that purpose we use the implicit router and define router.field=user. > > From what we've seen, the only way to define an implicit router is during > the collection creation. > Moreover, the router definitions (router.name and router.field) are kept > only in clusterstate.json and not in any solr configuration file on disk. > > In some cases solr state becomes inconsistent and we need to delete the > configs from ZK and restart the solr server. The behavior we see is the > new clusterstate.json generated by solr on startup has the default > router.name=compositeId, which is not what we defined during creation. > > Are we missing something? Is there a place to configure the implicit > router on disk such that it will be persistent? > > Thanks, > Arnon > >
