Details
-
Bug
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
4.10.1
-
None
-
None
-
Mac OS X
Description
Solr Collections API returns misleading error when trying to create two collections with the same name but with different case on MacOS file system (which is case insensitive).
sh> curl 'http://localhost:8983/solr/admin/collections?action=CREATE&name=test&numShards=1&collection.configName=default&indent=true&wt=json' { "responseHeader":{ "status":0, "QTime":1949}, "success":{ "":{ "responseHeader":{ "status":0, "QTime":1833}, "core":"test_shard1_replica1"}}} sh> curl 'http://localhost:8983/solr/admin/collections?action=CREATE&name=TEST&numShards=1&collection.configName=default&indent=true&wt=json' { "responseHeader":{ "status":0, "QTime":2509}, "failure":{ "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error CREATEing SolrCore 'TEST_shard1_replica1': Unable to create core [TEST_shard1_replica1] Caused by: Lock obtain timed out: NativeFSLock@/Users/alexey/Desktop/solr-4.10.1/node1/solr/test_shard1_replica1/data/index/write.lock"}}
See Lock obtain timed out exception. It will be more user friendly to check existence of instance dir test_shard1_replica1 and return something like "Node A has replica B that uses the same index directory" exception (instead of just trying to hijack that existing directory and then propagating the inexplicable lock exception that arises as a result).
Attachments
Issue Links
- relates to
-
SOLR-6478 need docs / tests of the "rules" as far as collection names go
- Open