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 2014/01/09 12:25:51 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=13866565#comment-13866565 ]
Ramkumar Aiyengar edited comment on SOLR-5213 at 1/9/14 11:25 AM:
------------------------------------------------------------------
Shalin, any objection to this patch going in? May be with SOLR-5338, the severity of the 0 shard case can be reduced from log.error (alternatively, it could check for split.key being present and decide severity if we want to be smarter), but the patch should good otherwise..
was (Author: andyetitmoves):
Shalin, any objection to this patch going in? May be with SOLR-5338, the severity of the 0 shard case can be reduced from log.error, but the patch should good otherwise..
> 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: Shalin Shekhar Mangar
> Attachments: 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.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org