[
https://issues.apache.org/jira/browse/HBASE-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520592#comment-14520592
]
Jonathan Hsieh commented on HBASE-13531:
----------------------------------------
and it looks like the master process has 291 threads that are sending on to
a1210.x.x.x:2181 -- most of which look like this
{code}
"MobFileCompactor-pool10-t1-SendThread(a1210.halxg.cloudera.com:2181)" daemon
prio=10 tid=0x00000000025f1000 nid=0x481c runnable [0x00007f03d0793000]
"MobFileCompactor-pool10-t1-SendThread(a1210.halxg.cloudera.com:2181)" daemon
prio=10 tid=0x0000000002679000 nid=0x480e runnable [0x00007f03d46d2000]
"MobFileCompactor-pool10-t1-SendThread(a1210.halxg.cloudera.com:2181)" daemon
prio=10 tid=0x0000000002adb000 nid=0x4800 runnable [0x00007f03d8a2b000]
{code}
> After 4/18/15 merge, flakey failures of
> TestAcidGuarantees#testMobScanAtomicity
> -------------------------------------------------------------------------------
>
> Key: HBASE-13531
> URL: https://issues.apache.org/jira/browse/HBASE-13531
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Affects Versions: hbase-11339
> Reporter: Jonathan Hsieh
> Fix For: hbase-11339
>
>
> After the merge of master from 4/18/15 with hbase-11339 branch, we encounter
> some atomicity violations. We want to fix before calling merge to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
