Thanks Jon.
When I'm back in the office I'll check out master and have a look into any
locally repeatable test failures. Anyway in my opinion at this point it
would make the most sense for us to keep the MOB changes in on master and
deal with any fallout in follow on issues. I think all who voted
Konstantin Shvachko created HBASE-14153:
---
Summary: Typo in ProcedureManagerHost.MASTER_PROCEUDRE_CONF_KEY
Key: HBASE-14153
URL: https://issues.apache.org/jira/browse/HBASE-14153
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John resolved HBASE-14151.
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks for noticing this and giving a quick
Hi Biju and Masatake,
I have a similar problem for my client htrace spans. I am not able to see
the parent client span in my trace output.
I have enabled htrace logging on server side using the below configuration
in hbase-site.xml
property
namehbase.trace.spanreceiver.classes/name
Jingcheng Du created HBASE-14152:
Summary: Fix the warnings in Checkstyle and FindBugs brought in by
merging hbase-11339
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
[
https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan reopened HBASE-12295:
Prevent block eviction under us if reads are in progress from the BBs
