[jira] [Created] (HBASE-28323) When AbstractRpcClient calls getConnection, the status of conn should be checked

2024-01-18 Thread Zhiwen Deng (Jira)
Zhiwen Deng created HBASE-28323: --- Summary: When AbstractRpcClient calls getConnection, the status of conn should be checked Key: HBASE-28323 URL: https://issues.apache.org/jira/browse/HBASE-28323 Projec

Re: HBASE-28242: Remove support for async-profiler v1

2024-01-18 Thread Andrew Purtell
I was the original developer of this feature. It existed in pretty much the same form in Hive and was a straightforward port. The style of using enums to encode and restrict supported parameters came from the origin. I thought it a good idea, though, because this shells out to an external proces

[jira] [Resolved] (HBASE-28316) Add BootstrapNodeService handlers

2024-01-18 Thread Duo Zhang (Jira)
[ https://issues.apache.org/jira/browse/HBASE-28316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28316. --- Fix Version/s: 2.6.0 3.0.0-beta-2 Hadoop Flags: Reviewed Resolution: F

Re: HBASE-28242: Remove support for async-profiler v1

2024-01-18 Thread Bryan Beaudreault
Yea, that makes sense and was the one reason I could think of as well. My concern with not backporting is that 3.x has been in development for many years, and all of our users are on 2.x (or even 1.x). Duo is making progress on 3.x now, but it's not clear when it will be released or, further, when

Re: HBASE-28242: Remove support for async-profiler v1

2024-01-18 Thread Lars Francke
Hi Bryan, good question. We can probably keep supporting v1 if we wanted to but I'm wondering if it's worth the effort (personally I think not). I do agree that it should not be backported! And I have wondered the same. If you look at the history of the issue I kinda proposed forwarding parameter

[jira] [Created] (HBASE-28322) Attach the design doc in HBASE-26220 to our code base

2024-01-18 Thread Duo Zhang (Jira)
Duo Zhang created HBASE-28322: - Summary: Attach the design doc in HBASE-26220 to our code base Key: HBASE-28322 URL: https://issues.apache.org/jira/browse/HBASE-28322 Project: HBase Issue Type: S

Re: HBASE-28242: Remove support for async-profiler v1

2024-01-18 Thread Bryan Beaudreault
Is it necessary to break support for v1? It would be fine to merge this to master and branch-3. But I think this change falls into the "Dependency Compatibility" portion of our compatibility guidelines[1]. If so, then we should not backport to branch-2 or 2.x. Generally, I have previously wondere

HBASE-28242: Remove support for async-profiler v1

2024-01-18 Thread Lars Francke
Hi, I just wanted to give a heads-up on an issue I created (thanks for everyone's help)[1] This would be a breaking change as it removes support for async-profiler v1 but in exchange it does add support for various v2 features and in general "unbreaks" things that were broken. I already have an