On 12/13/2017 10:08 PM, Nimesh Aghera wrote: > Currently using solr cloud 6.1.0 and below is the solr admin UI which shows > that routing changes after make upconfig command > > Below values shown in Solr Admin UI are before make re-upconfig where all > data are indexed into particular shard.
I could not reproduce this on Solr 7.1.0. If there *is* a problem in version 6.1.0, it's not going to get fixed. Versions that old will never see an update. First, I started up the cloud example with "bin\solr start -e cloud -nomprompt". This was on a Windows 7 system with Oracle Java 8u144. Then I made a Collections API call like yours to create a collection: http://localhost:8983/solr/admin/collections?action=CREATE&name=model&replicationFactor=2&router.name=implicit&router.field=title&shards=shard1,shard2&maxShardsPerNode=2&collection.configName=gettingstarted This is the response from that call: { "responseHeader":{ "status":0, "QTime":4971}, "success":{ "192.168.1.4:7574_solr":{ "responseHeader":{ "status":0, "QTime":2843}, "core":"model_shard2_replica_n6"}, "192.168.1.4:7574_solr":{ "responseHeader":{ "status":0, "QTime":3078}, "core":"model_shard1_replica_n2"}, "192.168.1.4:8983_solr":{ "responseHeader":{ "status":0, "QTime":3382}, "core":"model_shard2_replica_n4"}, "192.168.1.4:8983_solr":{ "responseHeader":{ "status":0, "QTime":3618}, "core":"model_shard1_replica_n1"}}} This is a screenshot of the collection overview, showing the implicit router: https://www.dropbox.com/s/x5gtpkkl6lv18g8/test1-collection-info-after-create.png?dl=0 Then I made a whitespace-only change to solrconfig.xml in the _default configset, and re-uploaded it to replace the configuration I used for the collection: bin\solr zk upconfig -d server\solr\configsets\_default -n gettingstarted -z localhost:9983 There was no difference at all in the collection details. I even did a collection reload, and still did not see anything change. Thanks, Shawn
