[
https://issues.apache.org/jira/browse/SOLR-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-5638.
--------------------------------
Resolution: Fixed
I'm closing this issue since it has already been fixed in some Solr version or
another; not sure which. I verified for sure in 6.x... and I see the check in
5.4 and it probably got added even prior to that.
(not sure what JIRA resolution is right for this scenario but I'll just use
"Fixed")
> Collection creation partially works, but results in unusable configuration
> due to missing config in ZK
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5638
> URL: https://issues.apache.org/jira/browse/SOLR-5638
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.6
> Reporter: Nathan Neulinger
> Attachments: SOLR-5638.patch
>
>
> Need help properly recovering from 'collection gets created without config
> being defined'.
> Right now, if you submit a collection create and the config is missing, it
> will proceed with partially creating cores, but then the cores fail to load.
> This requires manual intervention on the server to fix unless you pick a new
> colllection name:
> What's worse - if you retry the create a second time, it will usually try to
> create the replicas in the opposite order, resulting in TWO broken cores on
> each box, one for each attempted replica.
> beta1-newarch_hive1_v12_shard1_replica1:
> org.apache.solr.common.cloud.ZooKeeperException:org.apache.solr.common.cloud.ZooKeeperException:
> Specified config does not exist in ZooKeeper:hivepoint-unknown
> beta1-newarch_hive1_v12_shard1_replica2:
> org.apache.solr.common.cloud.ZooKeeperException:org.apache.solr.common.cloud.ZooKeeperException:
> Specified config does not exist in ZooKeeper:hivepoint-unknown
> I already know how to clear this up manually, but this is something where
> solr is allowing a condition in external service to result in a
> corrupted/partial configuration.
> I can see an easy option for resolving this as a workaround - allow a
> collection CREATE operation to specify "reuseCores" - i.e. allow it to use
> an existing core of the proper name if it already exists.
> Right now you wind up getting:
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
> CREATEing SolrCore 'beta1-newarch_hive1_v12_shard1_replica1': Could not
> create a new core in solr/beta1-newarch_hive1_v12_shard1_replica1/as another
> core is already defined there
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
> CREATEing SolrCore 'beta1-newarch_hive1_v12_shard1_replica2': Could not
> create a new core in solr/beta1-newarch_hive1_v12_shard1_replica2/as another
> core is already defined there
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
