hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6372) Add scanner batching to Export job
Date Mon, 30 Jul 2012 15:44:35 GMT

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

Jonathan Hsieh commented on HBASE-6372:
---------------------------------------

nit: 

can we also make this

{code}
+    int batching = Integer.parseInt(conf.get(EXPORT_BATCHING,"-1"));
{code}

the more canonical:

{code}
+    int batching = conf.getInt(EXPORT_BATCHING,-1));
{code}

before we commit?
                
> 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.96.0, 0.94.2
>            Reporter: Lars George
>            Assignee: Shengsheng Huang
>            Priority: Minor
>              Labels: newbie
>         Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message