You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Sami Siren (Created) (JIRA)" <ji...@apache.org> on 2012/01/30 13:27:10 UTC
[jira] [Created] (SOLR-3075) Overseer does not check cloudstate for
previously assigned shardId but generates a new one
Overseer does not check cloudstate for previously assigned shardId but generates a new one
------------------------------------------------------------------------------------------
Key: SOLR-3075
URL: https://issues.apache.org/jira/browse/SOLR-3075
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.0
Reporter: Sami Siren
Overseer does not check if core has already been assigned an shardId before assigning it a new shardId -> same core could end up having multiple shardIds in CloudState.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3075) Overseer does not check cloudstate for
previously assigned shardId but generates a new one
Posted by "Mark Miller (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3075:
------------------------------
Fix Version/s: 4.0
Assignee: Mark Miller
> Overseer does not check cloudstate for previously assigned shardId but generates a new one
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-3075
> URL: https://issues.apache.org/jira/browse/SOLR-3075
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-3075.patch
>
>
> Overseer does not check if core has already been assigned an shardId before assigning it a new shardId -> same core could end up having multiple shardIds in CloudState.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3075) Overseer does not check cloudstate
for previously assigned shardId but generates a new one
Posted by "Mark Miller (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-3075.
-------------------------------
Resolution: Fixed
Thanks Sami! Committed.
> Overseer does not check cloudstate for previously assigned shardId but generates a new one
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-3075
> URL: https://issues.apache.org/jira/browse/SOLR-3075
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-3075.patch
>
>
> Overseer does not check if core has already been assigned an shardId before assigning it a new shardId -> same core could end up having multiple shardIds in CloudState.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3075) Overseer does not check cloudstate for
previously assigned shardId but generates a new one
Posted by "Sami Siren (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sami Siren updated SOLR-3075:
-----------------------------
Attachment: SOLR-3075.patch
-fix + test
-also convert #testOverseerFailure to use MockZKController
> Overseer does not check cloudstate for previously assigned shardId but generates a new one
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-3075
> URL: https://issues.apache.org/jira/browse/SOLR-3075
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Attachments: SOLR-3075.patch
>
>
> Overseer does not check if core has already been assigned an shardId before assigning it a new shardId -> same core could end up having multiple shardIds in CloudState.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org