lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5214) collections?action=SPLITSHARD running out of heap space due to merge
Date Fri, 27 Dec 2013 08:38:51 GMT

    [ https://issues.apache.org/jira/browse/SOLR-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857384#comment-13857384
] 

ASF subversion and git services commented on SOLR-5214:
-------------------------------------------------------

Commit 1553645 from shalin@apache.org in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1553645 ]

SOLR-5214: Reduce memory usage for shard splitting by merging segments one at a time

> 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
>            Assignee: Shalin Shekhar Mangar
>         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 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


Mime
View raw message