Re: [DISCUSS] A plan for 2.4

On Wed, Oct 14, 2020 at 6:58 PM 张铎(Duo Zhang) wrote: > I do not think HBASE-18070 is a blocker for 2.4 as it is still on a feature > branch. > And in the title of several jiras we have something like 'root/meta', which > seems to me that the intention is to also solve something related to > split

[jira] [Resolved] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065

[ https://issues.apache.org/jira/browse/HBASE-25186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25186. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to master and branch-2. Thanks [~ram_krish] f

[jira] [Reopened] (HBASE-25093) the RSGroupBasedLoadBalancer#retainAssignment throws NPE

[ https://issues.apache.org/jira/browse/HBASE-25093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-25093: --- The RSGroupBasedLoadBalancer is different on branch-2.3, so cherry-pick does not work... Please provid

[jira] [Resolved] (HBASE-25093) the RSGroupBasedLoadBalancer#retainAssignment throws NPE

[ https://issues.apache.org/jira/browse/HBASE-25093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] niuyulin resolved HBASE-25093. -- Resolution: Fixed > the RSGroupBasedLoadBalancer#retainAssignment throws NPE > ---

Re: [DISCUSS] A plan for 2.4

I do not think HBASE-18070 is a blocker for 2.4 as it is still on a feature branch. And in the title of several jiras we have something like 'root/meta', which seems to me that the intention is to also solve something related to splittable meta, then I do not think the work can be done in the near

Re: [DISCUSS] A plan for 2.4

To meet Nick's objective of a 2.4 release in November, we could wait two or three weeks for the meta replica work to completely land. Will that be sufficient? On Wed, Oct 14, 2020 at 10:03 AM Huaxiang Sun wrote: > For meta replica work, the task jira is HBASE-18070 >

[jira] [Resolved] (HBASE-25117) ReplicationSourceShipper thread can not be finished

[ https://issues.apache.org/jira/browse/HBASE-25117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil resolved HBASE-25117. -- Resolution: Fixed Merged to master, then cherry picked into branch-2, branch-2

Re: [DISCUSS] A plan for 2.4

For meta replica work, the task jira is HBASE-18070 . The source side change has been committed, Endpoint change is under review. Meta Replica load balance support at client side is in progress. Thanks, Huaxiang On Wed, Oct 14, 2020 at 9:42 AM Ni

Re: [DISCUSS] A plan for 2.4

Thank you Andrew. I was of a similar mind -- if I'm doing 2.3, 2.4 would be only of minimal incremental overhead. It would probably encourage the early retirement of 2.3 :) Does anyone else have outstanding work they're hoping to see in 2.4? I'd love to see an initial RC posted in the first half o

Re: Recommended way of using HBase Cell Tags.

Thank you Ram for your response ! > For your case, is there a possibility to have yournew feature as a first class feature using Tags? Just asking? Could you elaborate what you mean by first class feature ? Rushabh Shah - Software Engineering SMTS | Salesforce - - Mobile: 213 422 9

Re: Recommended way of using HBase Cell Tags.

Hi Rushabh If I remember correctly, the decision was not to expose tags for clients directly. All the tags were used as internal to the cell formation at the server side (for eg ACL and Visibility labels). For your case, is there a possibility to have yournew feature as a first class feature usin

Recommended way of using HBase Cell Tags.

Hi Everyone, I want to understand how to use the Hbase Cell Tags feature. We have a use case to identify the source of deletes (not the same as authenticated kerberos user). I have added more details about my use case in HBASE-25118 . At my day job

[jira] [Created] (HBASE-25188) Mark all meta znode related methods as deprecated

Duo Zhang created HBASE-25188: - Summary: Mark all meta znode related methods as deprecated Key: HBASE-25188 URL: https://issues.apache.org/jira/browse/HBASE-25188 Project: HBase Issue Type: Sub-t

[jira] [Created] (HBASE-25187) Improve SizeCachedKV variants initialization

ramkrishna.s.vasudevan created HBASE-25187: -- Summary: Improve SizeCachedKV variants initialization Key: HBASE-25187 URL: https://issues.apache.org/jira/browse/HBASE-25187 Project: HBase

The master node for ci-hadoop.a.o is full again

All pre commit and nightly jobs can not be scheduled. Filed https://issues.apache.org/jira/browse/INFRA-20984 for it

[jira] [Resolved] (HBASE-25065) WAL archival to be done by a separate thread

[ https://issues.apache.org/jira/browse/HBASE-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25065. --- Hadoop Flags: Reviewed Resolution: Fixed > WAL archival to be done by a separate thread >

[jira] [Created] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065

ramkrishna.s.vasudevan created HBASE-25186: -- Summary: TestMasterRegionOnTwoFileSystems is failing after HBASE-25065 Key: HBASE-25186 URL: https://issues.apache.org/jira/browse/HBASE-25186 Pro