[
https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543832#comment-13543832
]
Hudson commented on HBASE-6372:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #329 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/329/])
HBASE-6694 Test scanner batching in export job feature from HBASE-6372
(Alexander Alten-Lorenz) (Revision 1428772)
Result = FAILURE
jmhsieh :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/Export.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
> Add scanner batching to Export job
> ----------------------------------
>
> Key: HBASE-6372
> URL: https://issues.apache.org/jira/browse/HBASE-6372
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 0.94.2, 0.96.0
> Reporter: Lars George
> Assignee: Shengsheng Huang
> Priority: Minor
> Labels: newbie
> Fix For: 0.96.0
>
> Attachments: HBASE-6372.2.patch, HBASE-6372.3.patch,
> HBASE-6372.4.patch, HBASE-6372.5.patch, HBASE-6372.patch
>
>
> When a single row is too large for the RS heap then an OOME can take out the
> entire RS. Setting scanner batching in custom scans helps avoiding this
> scenario, but for the supplied Export job this is not set.
> Similar to HBASE-3421 we can set the batching to a low number - or if needed
> make it a command line option.
--
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
