[jira] [Resolved] (HBASE-26848) Set java.io.tmpdir on mvn command when running jenkins job

[ https://issues.apache.org/jira/browse/HBASE-26848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26848. --- Resolution: Fixed Pushed an addendum to solve the problem. > Set java.io.tmpdir on mvn command when

Re: [DISCUSS] HBASE-26849 NPE caused by WAL Compression and Replication

Hi duo, I have submit a PR for the doc. Please kindly help me review it if it is convenient for you. Maybe need some polish. Thank you, Regards 张铎(Duo Zhang) 于2022年3月16日周三 18:36写道： > +1 on updating doc first. You can file an issue for the documentat

[jira] [Created] (HBASE-26858) Refactor TestMasterRegionOnTwoFileSystems to avoid dead loop

Duo Zhang created HBASE-26858: - Summary: Refactor TestMasterRegionOnTwoFileSystems to avoid dead loop Key: HBASE-26858 URL: https://issues.apache.org/jira/browse/HBASE-26858 Project: HBase Issue

Re: [DISCUSS] HBASE-26849 NPE caused by WAL Compression and Replication

I agree with Andrew that without a 'versioned' LRUCache, it is not easy to implement things correctly. And yes it will impact performance if we implement the 'versioned' logic, for example, using a buffer. But considering the real scenario, we do not always need to support rollback LRUCache. When

[jira] [Resolved] (HBASE-26852) --hadoop-profile is not honored in branch-2 PR builds

[ https://issues.apache.org/jira/browse/HBASE-26852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-26852. -- Resolution: Invalid I believe this was broken by the syntax error introduced and subsequently

[jira] [Reopened] (HBASE-26833) Avoid waiting to clear buffer usage of ReplicationSourceShipper when aborting the RS

[ https://issues.apache.org/jira/browse/HBASE-26833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-26833: --- Reopen for applying an addendum. It introduces NPE in TestReplicationSource.testTerminateClearsBuffer.

[jira] [Resolved] (HBASE-26833) Avoid waiting to clear buffer usage of ReplicationSourceShipper when aborting the RS

[ https://issues.apache.org/jira/browse/HBASE-26833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26833. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed addendum to branch-2.4+. > Avoid waiting to c

Re: [DISCUSS] How to expose configs for users to tune

Another thought I had which may be a compromise. In general I think we should avoid magic strings [1]. A good example of that is in ConnectionImplementation [2]. That doesn't mean we need to go in the full opposite direction of putting all constants into one class. I can understand the reasonable d

[jira] [Created] (HBASE-26859) Split TestSnapshotProcedure to several smaller tests

ruanhui created HBASE-26859: --- Summary: Split TestSnapshotProcedure to several smaller tests Key: HBASE-26859 URL: https://issues.apache.org/jira/browse/HBASE-26859 Project: HBase Issue Type: Improv

[jira] [Created] (HBASE-26860) Backport "HBASE-25681 Add a switch for server/table queryMeter" to branch-2.4

Bryan Beaudreault created HBASE-26860: - Summary: Backport "HBASE-25681 Add a switch for server/table queryMeter" to branch-2.4 Key: HBASE-26860 URL: https://issues.apache.org/jira/browse/HBASE-26860

[ANNOUNCE] end of maintenance (EOM) for Apache HBase 2.3 releases

Hi folks! The Apache HBase 2.3 release line reached the end of maintenance in October 2021. Our apologies for the late notification. The final release was 2.3.7 and is available from archive.apache.org. No further releases from branch-2.3 are planned. Users of HBase 2.3.z should upgrade to the c

[jira] [Resolved] (HBASE-26704) EOL HBase 2.3.x

[ https://issues.apache.org/jira/browse/HBASE-26704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-26704. - Resolution: Fixed > EOL HBase 2.3.x > --- > > Key: HBASE-26704 >

[DISCUSS] EOM 1.7 and branch-1? (proposal: 2022/07/21)

We previously discussed this topic on this thread: https://lists.apache.org/thread/hlp18jjjxxpf62spd8zkhmht23hmpljg Is it time to consider EOL of branch-1 and all 1.x releases ? There doesn't seem to be much developer interest in branch-1 beyond occasional maintenance. This is understandable.

Re: [DISCUSS] HBASE-26849 NPE caused by WAL Compression and Replication

If we can accept the performance degradation in the Replication process, then I have a solution that can completely solve this problem based on the existing implementation. See ReaderBase#seek: @Override public void seek(long pos) throws IOException { if (compressionContext != null && emptyCompr

Re: [DISCUSS] HBASE-26849 NPE caused by WAL Compression and Replication

So I think the first step is to introduce different implementations for different scenarios. And for replication, we could use your above approach to solve the problem first, and then we could try to use Andrew's approach to optimize. WDYT? 唐天航 于2022年3月18日周五 11:50写道： > If we can accept the per

Re: [DISCUSS] HBASE-26849 NPE caused by WAL Compression and Replication

Agree. Then I will modify HBASE-26849 according to this plan, and if it goes well, it will be submitted to branch-1 first next week. Also, if Andrew doesn't mind, I'd be more than happy to be involved in the follow-up renovation. Maybe we can discuss the details later. Thank you. 张铎(Duo Zhang) 于