[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347864#comment-14347864
]
zhangduo commented on HBASE-13150:
----------------------------------
The region moving of e2998ed5019dc219cc3c0112541c0cdf is not triggered by
client, it should be the balancer.
{noformat}
2015-03-03 22:17:04,713 INFO [Thread-268] master.HMaster(1171): balance
hri=testRegionTransitionOperations,yyy,1425421019650.e2998ed5019dc219cc3c0112541c0cdf.,
src=asf900.gq1.ygridcore.net,44226,1425421017118,
dest=asf900.gq1.ygridcore.net,45988,1425421016996
{noformat}
[~octo47], I do not think it is caused by table enabling because this is a
region moving, not just assigning.
There are 7 regions moving trigger by client
{noformat}
2015-03-03 22:17:04,011 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,,1425421019650.f0fadadca3541ee837977b545ecabba2.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,105 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,ccc,1425421019650.00fe88fb2e6ed600a05c96283ba13055.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,121 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,ddd,1425421019650.55adc74733629e36d79051d5ca9150b1.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,130 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,fff,1425421019650.a44832b7d6de27281a976a74dfff9c7b.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,140 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,jjj,1425421019650.6012302985744f8f91e8082742d1a033.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,149 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,nnn,1425421019650.30840d6dbbfc8512a13014e60ab758b3.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
2015-03-03 22:17:04,160 INFO [Thread-268] master.HMaster(1278):
Client=null/null move
hri=testRegionTransitionOperations,ooo,1425421019650.44abfcf09b9f08a8dbdfe9185747db34.,
src=asf900.gq1.ygridcore.net,45988,1425421016996,
dest=asf900.gq1.ygridcore.net,44226,1425421017118, running balancer
{noformat}
No e2998ed5019dc219cc3c0112541c0cdf. We turn on balancer at the end of test and
call master.balance, so it is possible that there is region in transition when
we disabling the table.
And I think the direct reason is we skip regions in transition when deploy
tasks, but we do not ignore these regions in waitUntilDone, so only a timeout
can let us deploy the new tasks for remaining regions and the default timeout
is 5 minutes thus we get a test timeout.
But I blamed the related code, seems there is nothing changed recently, so I do
not know the root reason why it becomes flaky only recently...
> TestMasterObserver failing disable table at end of test
> -------------------------------------------------------
>
> Key: HBASE-13150
> URL: https://issues.apache.org/jira/browse/HBASE-13150
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
>
> I see in
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK/6202/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestMasterObserver/testRegionTransitionOperations/
> , now we have added in timeouts, that we are failing to disable a table. It
> looks like table is disabled but regions are being opened on the disabled
> table still, like HBASE-6537
> Let me see if can figure why this happening. Will be back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
