You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Toke Eskildsen (JIRA)" <ji...@apache.org> on 2015/02/25 22:08:06 UTC
[jira] [Commented] (SOLR-7163) LogByteSizeMergePolicy
maxMergeSizeForForcedMerge default is negative
[ https://issues.apache.org/jira/browse/SOLR-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337204#comment-14337204 ]
Toke Eskildsen commented on SOLR-7163:
--------------------------------------
Oops. Thus should have been under LUCENE. Should I close this issue and make a new one?
> LogByteSizeMergePolicy maxMergeSizeForForcedMerge default is negative
> ---------------------------------------------------------------------
>
> Key: SOLR-7163
> URL: https://issues.apache.org/jira/browse/SOLR-7163
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 4.10.3, 5.0
> Reporter: Toke Eskildsen
> Priority: Minor
> Fix For: Trunk
>
> Attachments: SOLR-7163.patch
>
>
> The default value for {{maxMergeSizeForForcedMerge}} in the class {{LogByteSizeMergePolicy}} is {{Long.MAX_VALUE*1024*1024}} which overflows and becomes -1048576.
> As far as I can see this results in forced merges always failing to merge, but frankly this is so far from my area of interest that I will not take the time to create a proper unit test.
--
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