[
https://issues.apache.org/jira/browse/HBASE-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253008#comment-16253008
]
stack commented on HBASE-18357:
-------------------------------
Been working on these failures. They are interesting.
TestRegionCaching fails because the regionserver closing region can't report
into the master; it has one handler only running. hbase2 has RS do RPC into
Master now other than the heartbeating to report status. Master needs to be
able to take the call (This test suite had handler count == 1 for one test
only... odd. I moved it out to be its own test suite). Also exception thrown
when we try Put to a RegionServer was problematic. We had lost facility where
if a region is being moved, we'd throw a RegionMovedException. I fixed this.
Also, the exception now is RetriesExhaustedException rather than
RetriesExhaustedWithDetailsException. This may be a problem but has to do w/
changes allowing AsyncTable and Table share some client processing. Will keep
an eye on it.
Fixing above seems to have fixed TestMulti (as per Vladimir above).
Was working on TestClusterStatus. It fails because it depends on the old
multicast facility that broadcast to clients dead servers. Filed HBASE-19261
because I couldn't get it going again.. needs more attention. Patch coming...
> Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in
> HBASE-14614
> --------------------------------------------------------------------------------
>
> Key: HBASE-18357
> URL: https://issues.apache.org/jira/browse/HBASE-18357
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0-alpha-1
> Reporter: Stephen Yuan Jiang
> Assignee: Vladimir Rodionov
> Attachments: HBASE-18357-v1.patch
>
>
> The Core Proc-V2 AM change in HBASE-14614 disabled two tests inTestHCM:
> testMulti and testRegionCaching
> This JIRA tracks the work to enable them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
