[ 
https://issues.apache.org/jira/browse/SOLR-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Erickson resolved SOLR-7400.
----------------------------------
    Resolution: Invalid

This is both very old and almost certainly a configuration issue, dataDirs are 
not shared amongst multiple replicas on the same node.

> Collection creation fails when over-provisioning maxShardsPerNode > 1
> ---------------------------------------------------------------------
>
>                 Key: SOLR-7400
>                 URL: https://issues.apache.org/jira/browse/SOLR-7400
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.10.3
>         Environment: HDP 2.2 / HDP Search
>            Reporter: Hari Sekhon
>            Priority: Major
>
> When trying to overprovision shards I've encountered an issue before where 
> the additional shards are trying to use the same dataDir resulting in failure 
> to obtain locks for those additional shard replicas:
> {code}curl 
> 'http://host:8983/solr/admin/collections?action=CREATE&name=test&numShards=6&maxShardsPerNode=6&replicationFactor=2&wt=json&indent=true'
> {
>   "responseHeader":{
>     "status":0,
>     "QTime":3925},
>   "failure":{
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard1_replica2': Unable to create core 
> [test_shard1_replica2] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock",
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard6_replica1': Unable to create core 
> [test_shard6_replica1] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock",
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard5_replica2': Unable to create core 
> [test_shard5_replica2] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock",
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard2_replica1': Unable to create core 
> [test_shard2_replica1] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock",
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard3_replica2': Unable to create core 
> [test_shard3_replica2] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock",
>     
> "":"org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
>  CREATEing SolrCore 'test_shard4_replica1': Unable to create core 
> [test_shard4_replica1] Caused by: Lock obtain timed out: 
> NativeFSLock@/data1/solr/test/index/write.lock"},
>  "success":{
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3225},
>       "core":"test_shard5_replica1"},
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3234},
>       "core":"test_shard6_replica2"},
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3248},
>       "core":"test_shard1_replica1"},
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3433},
>       "core":"test_shard4_replica2"},
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3620},
>       "core":"test_shard3_replica1"},
>     "":{
>       "responseHeader":{
>         "status":0,
>         "QTime":3800},
>       "core":"test_shard2_replica2"}}}
> {code}
> It's not clear given this how you could have more than one shard per node to 
> pre-provision for anticipated node growth.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to