On 1/13/2017 5:46 PM, Chetas Joshi wrote: > One of the things I have observed is: if I use the collection API to > create a replica for that shard, it does not complain about the config > which has been set to ReplicationFactor=1. If replication factor was > the issue as suggested by Shawn, shouldn't it complain?
The replicationFactor value is used by exactly two things: initial collection creation, and autoAddReplicas. It will not affect ANY other command or operation, including ADDREPLICA. You can create MORE replicas than replicationFactor indicates, and there will be no error messages or warnings. In order to have a replica automatically added, your replicationFactor must be at least two, and the number of active replicas in the cloud for a shard must be less than that number. If that's the case and the expiration times have been reached without recovery, then Solr will automatically add replicas until there are at least as many replicas operational as specified in replicationFactor. > I would also like to mention that I experience some instance dirs > getting deleted and also found this open bug > (https://issues.apache.org/jira/browse/SOLR-8905) The description on that issue is incomprehensible. I can't make any sense out of it. It mentions the core.properties file, but the error message shown doesn't talk about the properties file at all. The error and issue description seem to have nothing at all to do with the code lines that were quoted. Also, it was reported on version 4.10.3 ... but this is going to be significantly different from current 6.x versions, and the 4.x versions will NOT be updated with bugfixes. Thanks, Shawn
