[ https://issues.apache.org/jira/browse/HBASE-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367673#comment-14367673 ]
Andrew Purtell edited comment on HBASE-13269 at 3/18/15 6:59 PM: ----------------------------------------------------------------- Since both [~stack] and [~lhofhansl] chimed in with regret about not presizing, I will update this to do a max of 100. New patch coming shortly. Please let me know if you like that better. was (Author: apurtell): Since both [~stack] and [~lhofhansl] chimed in with regret about not presizing, I will update this to do a min of 100. New patch coming shortly. Please let me know if you like that better. > Limit result array preallocation to avoid OOME with large scan caching values > ----------------------------------------------------------------------------- > > Key: HBASE-13269 > URL: https://issues.apache.org/jira/browse/HBASE-13269 > Project: HBase > Issue Type: Bug > Reporter: Andrew Purtell > Assignee: Andrew Purtell > Fix For: 1.0.1, 0.98.12 > > Attachments: HBASE-13269-0.98.patch, HBASE-13269-1.0.patch > > > Scan#setCaching(Integer.MAX_VALUE) will likely terminate the regionserver > with an OOME due to preallocation of the result array according to this > parameter. We should limit the preallocation to some sane value. Definitely > affects 0.98 (fix needed to HRegionServer) and 1.0.x (fix needed to > RsRPCServices), not sure about later versions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)