You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2010/11/10 01:17:06 UTC
[jira] Commented: (HBASE-3212) More testing of enable/disable
uncovered base condition not in place; i.e. that only one enable/disable
runs at a time
[ https://issues.apache.org/jira/browse/HBASE-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930379#action_12930379 ]
Jonathan Gray commented on HBASE-3212:
--------------------------------------
Looks like one of those lines may have gone over 80.
If for correctness we require only one thread in enable/disable executor pool, then how can we make it configurable? I know it's undocumented config just saying, we may just hard-code as 1 for now since it's only one supported.
Otherwise, +1, commit!
> More testing of enable/disable uncovered base condition not in place; i.e. that only one enable/disable runs at a time
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-3212
> URL: https://issues.apache.org/jira/browse/HBASE-3212
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.90.0
>
> Attachments: 3212.txt
>
>
> Testing, uncovered fact that master has 3 handlers currently for enable/disable/delete and modify when hbase-3112 was built on supposition that there was only one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.