You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christine Poerschke (JIRA)" <ji...@apache.org> on 2013/09/04 14:42:51 UTC
[jira] [Updated] (SOLR-5214) collections?action=SPLITSHARD running
out of heap space due to merge
[ https://issues.apache.org/jira/browse/SOLR-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christine Poerschke updated SOLR-5214:
--------------------------------------
Attachment: SOLR-5214.patch
Attaching patch against trunk, to not merge when splitting (i.e. no merge=true/false parameter as yet).
> collections?action=SPLITSHARD running out of heap space due to merge
> --------------------------------------------------------------------
>
> Key: SOLR-5214
> URL: https://issues.apache.org/jira/browse/SOLR-5214
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.3
> Reporter: Christine Poerschke
> Attachments: SOLR-5214.patch
>
>
> The problem we saw was that splitting a shard with many segments and documents
> failed by running out of heap space.
> Increasing heap space so that all existing segments could be merged into one
> overall segment does not seem practical. Running the split without segment
> merging worked.
> Could split always run without merging, or merge=true/false be an optional parameter for the SPLITSHARD action?
--
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