Re: [Discuss] Adding support for mapping namespaces to Region Server Groups

Hi Rajeshbabu, I'm not sure but could HBASE-24032 solve your problem? rajeshb...@apache.org 于2023年5月3日周三 13:03写道： rajeshb...@apache.org 于2023年5月3日周三 13:03写道： > Hi, > > Currently RS groups supports mapping the tables to a rsgroup and there

Re: [DISCUSS] Deprecated the 'hbase.regionserver.hlog.reader.impl' and 'hbase.regionserver.hlog.writer.impl' configurations

gt; replication abstraction too. > > Thanks. > > 唐天航 于2023年2月15日周三 11:42写道： > > > Can we keep these configs and add a new one for the replication reader? > > > > As @Andrew said, One of the things we are doing is using BookKeeper for > WAL > > stor

Re: [DISCUSS] Deprecated the 'hbase.regionserver.hlog.reader.impl' and 'hbase.regionserver.hlog.writer.impl' configurations

Can we keep these configs and add a new one for the replication reader? As @Andrew said, One of the things we are doing is using BookKeeper for WAL storage. This depends on the configuration above. Although we are developing based on branch-1, and it is too early to talk about joining the

[NOTICE] Compatibility issue between Replication and WAL Compression

At present, there is a compatibility problem if Replication and WAL Compression are used together. It might cause the WAL queue of replication to overstock. Branch-1, branch-2, master all be affected. See details in HBASE-26849 . We already have

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

) 于2022年3月18日周五 12:47写道： > 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?

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

nce for reading WAL > is not very critical then, so I think it is OK to implement rollback for > this scenario. > > So basically, I think we could have different LRUCache implementations, and > also different reader implementations, to suit different scenarios, then we > could gain

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

an issue for the documentation > change, and let's also send an NOTICE email to both dev and user list to > warn our users about this. > > 唐天航 于2022年3月16日周三 18:08写道： > > > If we only reset the position to the head, yes we can fix it. > > In fact, 26849 is to fix the problem in this scen

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

t; After > > that the integration tests would pass. > > > > However overall I would say we lack test coverage in this area. We should > > have a test scenario that is better at introducing short reads. > > > > I would agree there is an overall weakness with the WAL compr

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

BTW, I think this issue might also be helpful for HBASE-15983. 唐天航 于2022年3月17日周四 10:33写道： > Hi xiaolin, > > I have read HBASE-26843 just now. > > If you use WAL Compression, I think this issue might be related to > HBASE-26849. > When you get a NullPointerException or Inde

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

a WALEntryStreamRuntimeException and try again. At this layer the reader will be recreated (you will get a clean dict), and then you may find that there is no more log overstock. 唐天航 于2022年3月16日周三 23:10写道： > No problem, I will read the details about HBASE-26843 tomorrow. > And i think you

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

> > Regards > > 张铎(Duo Zhang) 于2022年3月16日周三 18:36写道： > > > +1 on updating doc first. You can file an issue for the documentation > > change, and let's also send an NOTICE email to both dev and user list to > > warn our users about this. > > > > 唐天航

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

> > Maybe we need to do some refactoring... > I can not agree more... But before that, I think we'd better point out this compatibility issue explicitly in our doc. 唐天航 于2022年3月16日周三 18:08写道： > If we only reset the position to the head, yes we can fix it. > In fact, 26849 is to

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

we need to do some refactoring... > > Thanks. > > 唐天航 于2022年3月16日周三 16:20写道： > > > Hi masters, > > > > I have created an issue HBASE-26849 > > <https://issues.apache.org/jira/browse/HBASE-26849> about NPE caused by > > WAL > > Compression and Replica

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

Hi masters, I have created an issue HBASE-26849 about NPE caused by WAL Compression and Replication. For this problem, I try to reopen a WAL reader when we reset the position to 0 and it looks like it's working well. But it didn't fundamentally

Re: [DISCUSS] HBASE-25299 Scan#setRowPrefixFilter Unexpected behavior

is nice find! > > > On Thu, 19 Nov 2020 at 6:02 AM, Guanghao Zhang wrote: > > > I am +1 to deprecated setRowPrefixFilter method. This method name is > > setRowPrefixFilter but not use filter and only set start row and end > row. I > > thought this could be done b

[DISCUSS] HBASE-25299 Scan#setRowPrefixFilter Unexpected behavior

Hi, I have open a issue HBASE-25299 about Scan#setRowPrefixFilter Unexpected behavior. e.g. startRow : "112" rowPrefixFilter : "11" The Result of this scan might contains : "111", which unexpected. public Scan setRowPrefixFilter(byte[]