You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2013/07/08 23:35:49 UTC
[jira] [Updated] (SOLR-4997) The splitshard api doesn't call commit
on new sub shards
[ https://issues.apache.org/jira/browse/SOLR-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-4997:
----------------------------------------
Attachment: SOLR-4997.patch
I found another bug while investigating this. Any core starting up as part of a "construction" shard was set to skip log replay but it also skipped recovery. So a subshard replica would publish itself as active without having any documents.
I also wasted a lot of time trying to figure out why a commit request would not work until I realized that HttpShardHandler is hardcoded to send QueryRequest so it cannot be used to issue a commit.
# Fix for above issue -- Only skip log replay but not recovery for cores belonging to "construction" state shards
# Call distrib commit before we switch shard states
# Tests for shard consistency
The test currently fails with sub shard leader having more docs than its replicas and I'm still trying to figure out why. My theory is that a newly created replica successfully recovers from leader but leader doesn't know about it and hence doesn't forward it any updates. If this is true then the replica may not sync for a long time. This might be another bug?
> The splitshard api doesn't call commit on new sub shards
> --------------------------------------------------------
>
> Key: SOLR-4997
> URL: https://issues.apache.org/jira/browse/SOLR-4997
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.3, 4.3.1
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.4
>
> Attachments: SOLR-4997.patch
>
>
> The splitshard api doesn't call commit on new sub shards but it happily sets them to active state which means on a successful split, the documents are not visible to searchers unless an explicit commit is called on the cluster.
> The coreadmin split api will still not call commit on targetCores. That is by design and we're not going to change that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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