[
https://issues.apache.org/jira/browse/SOLR-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447718#comment-16447718
]
ASF subversion and git services commented on SOLR-12250:
--------------------------------------------------------
Commit 4cd0a0aae329f62d440735f2a963ab8ba0e910bd in lucene-solr's branch
refs/heads/branch_7x from [~simonw]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4cd0a0a ]
SOLR-12250: Add missing assumeWorkingMockito call
> NegativeArraySizeException on TransactionLog if previous document more than
> 1.9GB
> ---------------------------------------------------------------------------------
>
> Key: SOLR-12250
> URL: https://issues.apache.org/jira/browse/SOLR-12250
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12250.patch, SOLR-12250.patch
>
>
> In TransactionLog, we have
> {code:java}
> bufSize = Math.min(1024*1024, lastAddSize+(lastAddSize>>3)+256);
> MemOutputStream out = new MemOutputStream(new byte[bufSize]);
> {code}
> Note that bufSize will be a negative number if lastAddSize > 1908874127 (
> which is around 1.9GB).
> Although this seems to relate to user's error because of sending such a big
> document. But the exception is thrown for the update after the big one.
> Therefore it is better to fix the problem and solving how we can prohibit
> users from sending very big documents in other issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
