[jira] [Resolved] (HBASE-27295) Correct the comment of list_deadservers method in admin.rb
[ https://issues.apache.org/jira/browse/HBASE-27295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tak-Lon (Stephen) Wu resolved HBASE-27295. -- Hadoop Flags: Reviewed Resolution: Fixed > Correct the comment of list_deadservers method in admin.rb > -- > > Key: HBASE-27295 > URL: https://issues.apache.org/jira/browse/HBASE-27295 > Project: HBase > Issue Type: Improvement > Components: shell >Affects Versions: 3.0.0-alpha-4 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Minor > Fix For: 3.0.0-alpha-4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Time for hbase-2.4.14 release
Thanks Duo. I am planning to spin 2.4.14RC0 on this Friday, if there is any jira you want to include in this RC, please backport them to branch-2.4 before this Friday. Thanks Huaxiang On Tue, Aug 16, 2022 at 8:11 PM 张铎(Duo Zhang) wrote: > Thanks for taking care of this! > > Huaxiang Sun 于2022年8月17日周三 02:33写道： > > > > Hi Folks, > > > > There are quite some critical fixes after 2.4.13, especially memory > > leaks in SASL implementation and ByteBuffAllocator. Since 2.5.0 release > is > > being worked on, there is a rolling back issue from 2.5.0 back to 2.4.* > > release which is fixed in the coming 2.4.14 release. 2.4.13 was released > on > > 7/1/22, it is about time for 2.4.14 release. > > > > Andrew is on PTO for two weeks. I volunteer to run this release > unless > > someone else wants to do. > > > > Please let me know if there are any concerns. > > > > Best Regards, > > Huaxiang >
Re: [DISCUSS] HBase 2.5 / Hadoop 3 artifacts
Hi Geoffrey, I have no complaints with shipping convenience binaries built against both Hadoop2 and Hadoop3. The primary challenge is implementing the necessary build changes, the secondary challenge is verifying/testing it works reliably. But for Phoenix, are you asking for convenience binaries, or are you asking for artifacts published into maven that have the Hadoop3 profile activated and specify the associated dependencies? I'm afraid that the 2.5.0 release ship has already sailed. I've heard talk of a 2.6 "fast-follow", so maybe someone can have the build changes ready for that? Also, isn't this a too little, too late situation? Shouldn't we shift our focus to releasing 3.0, which has dropped support for Hadoop2? Thanks, Nick On Tue, Aug 16, 2022 at 9:30 PM Geoffrey Jacoby wrote: > I see that the next HBase 2.5 RC is imminent, and before that's set in > stone, I wanted to bring up the question of whether there will be official > HBase 2.5 binaries built with the Hadoop 3 profile and available in the > usual Maven repositories. (In addition to the usual Hadoop 2 profile > binaries) > > The HBase 2.x line has a commitment to maintain support for Hadoop 2.x, but > Hadoop 3.3 is the current stable Hadoop line and the most recent release > notes [1] encourage all users of Hadoop 2.x to upgrade to Hadoop 3. > > Without convenience artifacts built against Hadoop 3, no end-users with > Hadoop 3 clusters will be able to use the Apache-distributed binaries and > will instead have to recompile HBase from source themselves, or use a 3rd > party distribution that does so for them. > > This is especially inconvenient for downstream projects such as Apache > Phoenix, which has never officially supported the HBase 2.x / Hadoop 2.10 > combination. (It currently supports only HBase 2.3 or 2.4 with Hadoop 3. > HBase 2.5 support will be added very shortly after its release as part of > Phoenix 5.2.) > > To even run the Phoenix IT tests locally requires contributors to download > the HBase source release and manually mvn install to their local maven repo > using the Hadoop 3 profile, to avoid crashes in the HBase minicluster.[2] > This is a barrier to new contributors and confuses even veteran ones, and > has to be done again for every new HBase release. > > In general, I expect the Hadoop 3 user base to grow and the Hadoop 2.10 > user base to shrink with every future HBase 2 release, so I think this is a > worthwhile improvement. > > Thanks, > > Geoffrey > > [1] https://hadoop.apache.org/release/3.3.4.html > [2] https://github.com/apache/phoenix/blob/master/BUILDING.md >
[jira] [Resolved] (HBASE-24163) MOB compactor implementations should use format specifiers when calling String.format
[ https://issues.apache.org/jira/browse/HBASE-24163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-24163. -- Resolution: Fixed Merged to branch-2 and branch-2.5. > MOB compactor implementations should use format specifiers when calling > String.format > - > > Key: HBASE-24163 > URL: https://issues.apache.org/jira/browse/HBASE-24163 > Project: HBase > Issue Type: Bug > Components: Compaction, mob >Affects Versions: 3.0.0-alpha-1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 2.5.0, 3.0.0-alpha-1 > > > HBASE-23723 includes a few IOException message constructions that rely on > String.format but use slf4j parameters instead of format specifiers. > Discovered by nightly failing error-prone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-24163) MOB compactor implementations should use format specifiers when calling String.format
[ https://issues.apache.org/jira/browse/HBASE-24163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-24163: -- Reopened for branch-2.5+ banckports. > MOB compactor implementations should use format specifiers when calling > String.format > - > > Key: HBASE-24163 > URL: https://issues.apache.org/jira/browse/HBASE-24163 > Project: HBase > Issue Type: Bug > Components: Compaction, mob >Affects Versions: 3.0.0-alpha-1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0-alpha-1 > > > HBASE-23723 includes a few IOException message constructions that rely on > String.format but use slf4j parameters instead of format specifiers. > Discovered by nightly failing error-prone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
