You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ramkumar Aiyengar (JIRA)" <ji...@apache.org> on 2015/04/26 02:02:34 UTC
[jira] [Updated] (SOLR-5213) collections?action=SPLITSHARD parent
vs. sub-shards numDocs
[ https://issues.apache.org/jira/browse/SOLR-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramkumar Aiyengar updated SOLR-5213:
------------------------------------
Attachment: SOLR-5213.patch
Brought this up to date and fixed a bug when ranges is null..
> collections?action=SPLITSHARD parent vs. sub-shards numDocs
> -----------------------------------------------------------
>
> Key: SOLR-5213
> URL: https://issues.apache.org/jira/browse/SOLR-5213
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.4
> Reporter: Christine Poerschke
> Assignee: Ramkumar Aiyengar
> Attachments: SOLR-5213.patch, SOLR-5213.patch
>
>
> The problem we saw was that splitting a shard took a long time and at the end of it the sub-shards contained fewer documents than the original shard.
> The root cause was eventually tracked down to the disappearing documents not falling into the hash ranges of the sub-shards.
> Could SolrIndexSplitter split report per-segment numDocs for parent and sub-shards, with at least a warning logged for any discrepancies (documents falling into none of the sub-shards or documents falling into several sub-shards)?
> Additionally, could a case be made for erroring out when discrepancies are detected i.e. not proceeding with the shard split? Either to always error or to have an verifyNumDocs=false/true optional parameter for the SPLITSHARD action.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org