[
https://issues.apache.org/jira/browse/HBASE-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Vashishtha updated HBASE-7607:
---------------------------------------
Description:
TestRegionServerCoprocessorExceptionWithAbort fails sometimes both on trunk and
0.94.X. The codebase is different in both.
In 0.94.x, client retries to look at the root region, while the cluster is down
and /hbase znode is no longer present.
"Check the value configured in 'zookeeper.znode.parent'. There could be a
mismatch with the one configured in the master."
I will file a separate jira for the trunk as the code is different there.
was:
TestRegionServerCoprocessorExceptionWithAbort fails sometimes both on trunk and
0.94.X. The codebase is different in both.
In trunk, table.put() passes even with BuggyRegionCoprocessor failed the
transaction:
"The put should have failed, as the coprocessor is buggy"
In 0.94.x, client retries to look at the root region, while the cluster is down
and /hbase znode is no longer present.
"Check the value configured in 'zookeeper.znode.parent'. There could be a
mismatch with the one configured in the master."
Fix Version/s: 0.94.5
Summary: Fix TestRegionServerCoprocessorExceptionWithAbort flakiness
in 0.94 (was: Fix TestRegionServerCoprocessorExceptionWithAbort flakiness )
> Fix TestRegionServerCoprocessorExceptionWithAbort flakiness in 0.94
> -------------------------------------------------------------------
>
> Key: HBASE-7607
> URL: https://issues.apache.org/jira/browse/HBASE-7607
> Project: HBase
> Issue Type: Bug
> Components: Client, test
> Affects Versions: 0.94.4
> Reporter: Himanshu Vashishtha
> Assignee: Himanshu Vashishtha
> Fix For: 0.94.5
>
>
> TestRegionServerCoprocessorExceptionWithAbort fails sometimes both on trunk
> and 0.94.X. The codebase is different in both.
> In 0.94.x, client retries to look at the root region, while the cluster is
> down and /hbase znode is no longer present.
> "Check the value configured in 'zookeeper.znode.parent'. There could be a
> mismatch with the one configured in the master."
> I will file a separate jira for the trunk as the code is different there.
--
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
