You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2012/05/16 08:30:12 UTC
[jira] [Created] (BIGTOP-589) TestLoadAndVerify's HBase scanner
caching setting too high
Jonathan Hsieh created BIGTOP-589:
-------------------------------------
Summary: TestLoadAndVerify's HBase scanner caching setting too high
Key: BIGTOP-589
URL: https://issues.apache.org/jira/browse/BIGTOP-589
Project: Bigtop
Issue Type: Bug
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Currently the default HBase Scanner Caching setting pulls 5000 rows in at time. In long term testing this value seems to be too large and prone to TT job failures due to ScannerTimeouts. This value should be lowered by default and parameterized (when run as main as a system test).
--
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
[jira] [Updated] (BIGTOP-589) TestLoadAndVerify's HBase scanner
caching setting too high
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated BIGTOP-589:
----------------------------------
Attachment: bigtop-589.patch
Parameterizes scanner caching and changes default to lower, safer number.
> TestLoadAndVerify's HBase scanner caching setting too high
> ----------------------------------------------------------
>
> Key: BIGTOP-589
> URL: https://issues.apache.org/jira/browse/BIGTOP-589
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Labels: hbase
> Fix For: 0.4.0
>
> Attachments: bigtop-589.patch
>
>
> Currently the default HBase Scanner Caching setting pulls 5000 rows in at time. In long term testing this value seems to be too large and prone to TT job failures due to ScannerTimeouts. This value should be lowered by default and parameterized (when run as main as a system test).
--
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
[jira] [Commented] (BIGTOP-589) TestLoadAndVerify's HBase scanner
caching setting too high
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278008#comment-13278008 ]
Roman Shaposhnik commented on BIGTOP-589:
-----------------------------------------
+1 and committed. Thanks a bunch for the patch!
> TestLoadAndVerify's HBase scanner caching setting too high
> ----------------------------------------------------------
>
> Key: BIGTOP-589
> URL: https://issues.apache.org/jira/browse/BIGTOP-589
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Labels: hbase
> Fix For: 0.4.0
>
> Attachments: bigtop-589.patch
>
>
> Currently the default HBase Scanner Caching setting pulls 5000 rows in at time. In long term testing this value seems to be too large and prone to TT job failures due to ScannerTimeouts. This value should be lowered by default and parameterized (when run as main as a system test).
--
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