[DISCUSS] About tracing in HBase

2021-01-21 Thread Duo Zhang
In HBASE-22120, I tried to use OpenTelemetry to replace HTrace in HBase, and it is basically done. https://github.com/apache/hbase/pull/2901 I've filed HBASE-25526 for later improvement. The remaining works for HBASE-22120 are 1. Enabling trace on a real cluster, to test whether the whole flow

[jira] [Resolved] (HBASE-23759) [OpenTracing] Migrate hbase shell and scripts from HTrace to OpenTracing

2021-01-21 Thread Duo Zhang (Jira)
[ https://issues.apache.org/jira/browse/HBASE-23759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-23759. --- Resolution: Won't Fix > [OpenTracing] Migrate hbase shell and scripts from HTrace to OpenTracing >

[jira] [Created] (HBASE-25526) Implement more detailed tracing in HBase

2021-01-21 Thread Duo Zhang (Jira)
Duo Zhang created HBASE-25526: - Summary: Implement more detailed tracing in HBase Key: HBASE-25526 URL: https://issues.apache.org/jira/browse/HBASE-25526 Project: HBase Issue Type: Umbrella

[jira] [Resolved] (HBASE-25484) Add trace support for WAL sync

2021-01-21 Thread Duo Zhang (Jira)
[ https://issues.apache.org/jira/browse/HBASE-25484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25484. --- Fix Version/s: HBASE-22120 Hadoop Flags: Reviewed Resolution: Fixed Merged to branch

[jira] [Created] (HBASE-25525) WALKey Extended Attributes don't serialize to ReplicationSink

2021-01-21 Thread Geoffrey Jacoby (Jira)
Geoffrey Jacoby created HBASE-25525: --- Summary: WALKey Extended Attributes don't serialize to ReplicationSink Key: HBASE-25525 URL: https://issues.apache.org/jira/browse/HBASE-25525 Project: HBase

[jira] [Created] (HBASE-25524) Region Servers should give some indication that short-circuit reads are configured properly and working

2021-01-21 Thread Nick Dimiduk (Jira)
Nick Dimiduk created HBASE-25524: Summary: Region Servers should give some indication that short-circuit reads are configured properly and working Key: HBASE-25524 URL:

Re: [VOTE] HBase 2.3.4 release candidate (RC4) is available

2021-01-21 Thread Huaxiang Sun
We have enough affirmative votes (4 binding +1s) to close this vote and the vote is open for over 72 hours. If there are any pending tests/votes please let me know. Otherwise I will be closing this vote tomorrow morning Pacific time. On Wed, Jan 20, 2021 at 9:31 PM Stack wrote: > +1 (binding) >

Re: [VOTE] Third release candidate for HBase 2.4.1 (RC2) is available

2021-01-21 Thread Nick Dimiduk
+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_275): ok - mvn clean apache-rat:check -D skipTests * Rat check (11.0.8): ok - mvn clean apache-rat:check -D skipTests -D hadoop.profile=3.0 * Built from source (1.8.0_275): ok - mvn clean install -D skipTests -DskipTests * Built from source

Re: [VOTE] Third release candidate for HBase 2.4.1 (RC2) is available

2021-01-21 Thread Nick Dimiduk
On Wed, Jan 20, 2021 at 10:04 PM Stack wrote: > * Poked around the UI (We need to fix this: 2.4.1, revision=Unknown as our > version in UI) > Do you have this in the binary artifacts or in the artifacts built from the source release? It's expected for an artifact built from the source release,

Re: [VOTE] Third release candidate for HBase 2.4.1 (RC2) is available

2021-01-21 Thread Andrew Purtell
When I released 2.4.0 I extended the lifetime of this code signing key and updated KEYS, FWIW. Maybe you need to re-import? If it continues to be an issue for people I'll make a new key for the next one. Thanks Stack. > On Jan 20, 2021, at 10:04 PM, Stack wrote: > > +1 (binding) > > *

[jira] [Created] (HBASE-25523) Region normalizer chore thread is getting killed

2021-01-21 Thread Aman Poonia (Jira)
Aman Poonia created HBASE-25523: --- Summary: Region normalizer chore thread is getting killed Key: HBASE-25523 URL: https://issues.apache.org/jira/browse/HBASE-25523 Project: HBase Issue Type:

HBase Quarterly report Oct-Dec 2020

2021-01-21 Thread Duo Zhang
Hi all, HBase submits a report to the ASF board once a quarter, to inform the board about project health. I'm sending the report to the user@ and dev@ mailing lists because you are the project, and for transparency. If you have any questions about the report or the running of the project, you can