Re: [DISCUSS] Implement and release HBASE-24749 (an hfile tracker that allows for avoiding renames)

HBASE-24749 design and implementation had acknowledged compromises on review: e.g. adding a new 'system table' to hold store files. I'd suggest the design and implementation need a revisit before we go forward; for instance, factoring for systems other than s3 as suggested above (I like the Duo

Re: Time for 3.0.0 release

I'm happy to see us moving forward with hbase 3 release. If a feature makes it into alpha releases but under evaluation doesn't look ready for use, what's the plan? Back things out and put it into a feature branch? What about making releases out of the master branch until we stabilize the API by

Re: [DISCUSS] Implement and release HBASE-24749 (an hfile tracker that allows for avoiding renames)

So maybe we could introduce a .hfilelist directory, and put the hflielist files under this directory, so we do not need to list all the files under the region directory. And considering the possible implementation for typical object storages, listing the last directory on the whole path will be

Re: [DISCUSS] Implement and release HBASE-24749 (an hfile tracker that allows for avoiding renames)

> On May 21, 2021, at 6:07 PM, 张铎 wrote: > > Since we just make use of the general FileSystem API to do listing, is it > possible to make use of ' bucket index listing'? Yes, those words mean the same thing. > > Andrew Purtell 于2021年5月22日周六 上午6:34写道： > >> >> >>> On May 20, 2021, at

[jira] [Resolved] (HBASE-12341) Overhaul logging; log4j2, machine-readable, etc.

[ https://issues.apache.org/jira/browse/HBASE-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-12341. --- Resolution: Fixed All sub tasks have been resolved, so resolve. As different sub tasks has

Re: Time for 3.0.0 release

Oh, I forgot a big break change, moving to log4j2. 张铎(Duo Zhang) 于2021年5月21日周五 下午11:10写道： > Since favored nodes is an existing feature, an improvement for an existing > feature can come in at a minor release I think, unless you plan to > completely break the compatibility. > > Mallikarjun

[jira] [Resolved] (HBASE-19587) [sfl4j] " Class path contains multiple SLF4J binding" complaint

[ https://issues.apache.org/jira/browse/HBASE-19587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-19587. --- Resolution: Not A Problem Resolve as 'Not A Problem'. We have exclude all the slf4j-log4j12

Re: [DISCUSS] Implement and release HBASE-24749 (an hfile tracker that allows for avoiding renames)

Since we just make use of the general FileSystem API to do listing, is it possible to make use of ' bucket index listing'? Andrew Purtell 于2021年5月22日周六 上午6:34写道： > > > > On May 20, 2021, at 4:00 AM, Wellington Chevreuil < > wellington.chevre...@gmail.com> wrote: > > > >  > >> > >> > >> IMO it

[jira] [Resolved] (HBASE-25848) Add flexibility to backup replication in case replication filter throws an exception

[ https://issues.apache.org/jira/browse/HBASE-25848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Pal resolved HBASE-25848. - Resolution: Fixed > Add flexibility to backup replication in case replication filter throws an

Re: [DISCUSS] Implement and release HBASE-24749 (an hfile tracker that allows for avoiding renames)

> On May 20, 2021, at 4:00 AM, Wellington Chevreuil > wrote: > >  >> >> >> IMO it should be a file per store. >> Per region is not suitable here as compaction is per store. >> Per file means we still need to list all the files. And usually, after >> compaction, we need to do an atomic

[jira] [Resolved] (HBASE-25827) Per Cell TTL tags get duplicated with increments causing tags length overflow

[ https://issues.apache.org/jira/browse/HBASE-25827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-25827. -- Fix Version/s: 2.4.4 2.5.0 3.0.0-alpha-1 Hadoop

[jira] [Resolved] (HBASE-25682) Add a new command to update the configuration of all RSs in a RSGroup

[ https://issues.apache.org/jira/browse/HBASE-25682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pankaj Kumar resolved HBASE-25682. -- Fix Version/s: 2.5.0 3.0.0-alpha-1 Release Note: Added

Re: Time for 3.0.0 release

Since favored nodes is an existing feature, an improvement for an existing feature can come in at a minor release I think, unless you plan to completely break the compatibility. Mallikarjun 于2021年5月21日周五 下午10:11写道： > For multi tenancy with favoured nodes, timeline looks unreasonable for 3.0. >

Re: Time for 3.0.0 release

For multi tenancy with favoured nodes, timeline looks unreasonable for 3.0. Can it be part of later 3.x releases? Or should it wait for 4.0? On Fri, May 21, 2021, 7:30 PM 张铎(Duo Zhang) wrote: > We already have the below big feature/changes for 3.0.0. > > Synchronous Replication > OpenTelemetry

Time for 3.0.0 release

We already have the below big feature/changes for 3.0.0. Synchronous Replication OpenTelemetry Tracing Distributed MOB Compaction Backup and Restore Move RSGroup balancer to core Reimplement sync client on async client CPEPs on shaded proto There are also some ongoing works which target 3.0.0.