[jira] [Created] (HBASE-21999) [DEBUG] Exit if git returns empty revision!
stack created HBASE-21999: - Summary: [DEBUG] Exit if git returns empty revision! Key: HBASE-21999 URL: https://issues.apache.org/jira/browse/HBASE-21999 Project: HBase Issue Type: Sub-task Reporter: stack Let me commit a bit of debug on branch-2.0. Can't figure out how we are getting empty git revision string. Have the build fail if empty -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-22000) Deprecated isTableAvailable with splitKeys
Duo Zhang created HBASE-22000: - Summary: Deprecated isTableAvailable with splitKeys Key: HBASE-22000 URL: https://issues.apache.org/jira/browse/HBASE-22000 Project: HBase Issue Type: Sub-task Components: asyncclient, Client Reporter: Duo Zhang It is deprecated in Admin interface and plan to be removed in 3.0.0 release, we should do this for AsyncAdmin interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
A question about contributions
Good morning everyone! A beginner contributor here. I have a question about contribution process. I would like to submit a small change. I followed this process: 1. Cloned the repo 2. Did my change in the master branch 3. Made a commit to master branch with a message format like this: "HBASE- Commit message" 4. Ran "dev-support/submit-patch.py -jid HBASE- -srb" (My patch is really small so I omitted a review-board option) * I provided my jira credentials when asked 5. submit-patch.py returned 403 error I guess I don't have permissions to attach patches to jiras. What I did wrong? Thanks!
Re: A question about contributions
Seems jira is back, please post on HBASE-21774 so I can get your jira account? Search 'Dmitriy Kuharev' returns nothing. Thanks. 张铎(Duo Zhang) 于2019年3月6日周三 下午3:48写道： > Sorry I've been rate limited by the jira server... Will do it later... > > Dmitriy Kuharev 于2019年3月6日周三 下午3:45写道： > >> The jira id: >> HBASE-21774 >> >> От: 张铎(Duo Zhang) >> Отправлено: 6 марта 2019 г. 10:44 >> Кому: HBase Dev List >> Тема: Re: A question about contributions >> >> What is the jira id? I can add you as a contributor so can assign the >> issue >> to you. >> >> Thanks. >> >> Dmitriy Kuharev 于2019年3月6日周三 >> 下午3:39写道： >> >> > Good morning everyone! >> > A beginner contributor here. >> > >> > I have a question about contribution process. >> > I would like to submit a small change. >> > I followed this process: >> > >> > 1. Cloned the repo >> > 2. Did my change in the master branch >> > 3. Made a commit to master branch with a message format like this: >> > "HBASE- Commit message" >> > 4. Ran "dev-support/submit-patch.py -jid HBASE- -srb" (My patch >> is >> > really small so I omitted a review-board option) >> > * I provided my jira credentials when asked >> > 5. submit-patch.py returned 403 error >> > >> > I guess I don't have permissions to attach patches to jiras. What I did >> > wrong? >> > Thanks! >> > >> >
[jira] [Resolved] (HBASE-21999) [DEBUG] Exit if git returns empty revision!
[ https://issues.apache.org/jira/browse/HBASE-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21999. --- Resolution: Fixed Pushed below on branch-2.0. Revert when figure the issue. diff --git a/hbase-common/src/saveVersion.sh b/hbase-common/src/saveVersion.sh index 730224f0d6..0136fecd60 100644 --- a/hbase-common/src/saveVersion.sh +++ b/hbase-common/src/saveVersion.sh @@ -45,6 +45,10 @@ else revision="Unknown" url="file://$cwd" fi +if [ -z $revision ] + echo "$revision is empty!" + exit 1 +fi > [DEBUG] Exit if git returns empty revision! > --- > > Key: HBASE-21999 > URL: https://issues.apache.org/jira/browse/HBASE-21999 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Priority: Major > > Let me commit a bit of debug on branch-2.0. Can't figure out how we are > getting empty git revision string. Have the build fail if empty -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: A question about contributions
Sorry I've been rate limited by the jira server... Will do it later... Dmitriy Kuharev 于2019年3月6日周三 下午3:45写道： > The jira id: > HBASE-21774 > > От: 张铎(Duo Zhang) > Отправлено: 6 марта 2019 г. 10:44 > Кому: HBase Dev List > Тема: Re: A question about contributions > > What is the jira id? I can add you as a contributor so can assign the issue > to you. > > Thanks. > > Dmitriy Kuharev 于2019年3月6日周三 下午3:39写道： > > > Good morning everyone! > > A beginner contributor here. > > > > I have a question about contribution process. > > I would like to submit a small change. > > I followed this process: > > > > 1. Cloned the repo > > 2. Did my change in the master branch > > 3. Made a commit to master branch with a message format like this: > > "HBASE- Commit message" > > 4. Ran "dev-support/submit-patch.py -jid HBASE- -srb" (My patch is > > really small so I omitted a review-board option) > > * I provided my jira credentials when asked > > 5. submit-patch.py returned 403 error > > > > I guess I don't have permissions to attach patches to jiras. What I did > > wrong? > > Thanks! > > >
Re: A question about contributions
What is the jira id? I can add you as a contributor so can assign the issue to you. Thanks. Dmitriy Kuharev 于2019年3月6日周三 下午3:39写道： > Good morning everyone! > A beginner contributor here. > > I have a question about contribution process. > I would like to submit a small change. > I followed this process: > > 1. Cloned the repo > 2. Did my change in the master branch > 3. Made a commit to master branch with a message format like this: > "HBASE- Commit message" > 4. Ran "dev-support/submit-patch.py -jid HBASE- -srb" (My patch is > really small so I omitted a review-board option) > * I provided my jira credentials when asked > 5. submit-patch.py returned 403 error > > I guess I don't have permissions to attach patches to jiras. What I did > wrong? > Thanks! >
RE: A question about contributions
The jira id: HBASE-21774 От: 张铎(Duo Zhang) Отправлено: 6 марта 2019 г. 10:44 Кому: HBase Dev List Тема: Re: A question about contributions What is the jira id? I can add you as a contributor so can assign the issue to you. Thanks. Dmitriy Kuharev 于2019年3月6日周三 下午3:39写道： > Good morning everyone! > A beginner contributor here. > > I have a question about contribution process. > I would like to submit a small change. > I followed this process: > > 1. Cloned the repo > 2. Did my change in the master branch > 3. Made a commit to master branch with a message format like this: > "HBASE- Commit message" > 4. Ran "dev-support/submit-patch.py -jid HBASE- -srb" (My patch is > really small so I omitted a review-board option) > * I provided my jira credentials when asked > 5. submit-patch.py returned 403 error > > I guess I don't have permissions to attach patches to jiras. What I did > wrong? > Thanks! >
[jira] [Created] (HBASE-21995) Add a coprocessor to set HDFS ACL for hbase granted user
Yi Mei created HBASE-21995: -- Summary: Add a coprocessor to set HDFS ACL for hbase granted user Key: HBASE-21995 URL: https://issues.apache.org/jira/browse/HBASE-21995 Project: HBase Issue Type: Sub-task Reporter: Yi Mei To make hbase granted user have the access to scan table snapshots, use HDFS ACLs to set user read permission over hfiles. The basic implementation is: 1. For public directories such as 'data' and 'archive', set other users' permission to '--x' to make everyone have the permission to access the directory. 2. For namespace or table directories such as 'data/ns/table', 'archive/ns/table' and '.hbase-snapshot/snapshotName', set user 'r-x' acl and default 'r-x' acl when following operations happen: grant to namespace or table / revoke from namespace or table / snapshot table For more details, please reference the design doc: https://docs.google.com/document/d/1D2iAdbrW5CcKc2SthJBXA1n2tTMTftuVaFtxbOWFuqM/edit#heading=h.uwo33s7kz427 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21996) Set locale for javadoc
Peter Somogyi created HBASE-21996: - Summary: Set locale for javadoc Key: HBASE-21996 URL: https://issues.apache.org/jira/browse/HBASE-21996 Project: HBase Issue Type: Improvement Components: documentation Reporter: Peter Somogyi Assignee: Peter Somogyi Headers in generated javadoc could have different language based on the user's locale. For example the published 2.1 javadoc's headers are in Chinese while 2.0 is in English. 2.0: [https://hbase.apache.org/2.0/apidocs/org/apache/hadoop/hbase/client/HTable.html] 2.1: [https://hbase.apache.org/2.1/apidocs/org/apache/hadoop/hbase/client/HTable.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: View on version EOLs
Both branch 1 and 2 will continue to have new releases where new features can be integrated, although, most of the contributions are shifting towards branch-2 lately. We're looking forward to your contributions! Peter On Mon, Mar 4, 2019 at 4:38 PM Nikhil Bafna wrote: > So, are there any 1.x branches that are continuing to get new features? > > Looking at a 6 month view, should we (Flipkart) rather plan to develop (and > start contributing) on 2.x branch, instead of 1.x branches? > > > -- > Nikhil Bafna | 8095234263 > > > On Fri, Mar 1, 2019 at 4:43 PM Peter Somogyi wrote: > > > The current plan is to retire 2.0. The voting is in progress for 2.0.5 > and > > more releases are not planned unless critical bugs are discovered. > > > > On the 1.3 line there was a discussion for EOL, but the Francis (RM) > would > > like to continue that. > > > > HBase 1.5.0 is coming up shortly and you could also expect more bugfix > > releases on 1.2. > > > > On Thu, Feb 28, 2019 at 6:38 AM Nikhil Bafna wrote: > > > > > We run Hbase 1.2.x in our production that has a set of patches & > > backports. > > > > > > In the mailing list, I see discussions for EOL of 1.3 & 2.0.x. In > another > > > mailing list discussion, it was pointed out that "... targeting only > bug > > > fixes for branch-1, as version 1 approaches EOL" > > > > > > But, I see new releases happening on 1.2.x versions - which seems to be > > > contradictory. > > > > > > What are the EOL plans for the active versions? > > > > > >
Request for an invite to Slack Channel
Hello, I would like to join the discussion in your slack channel. I have a few questions about submitting changes. Best Regards, Dmitriy.
Re: View on version EOLs
Hi Nikhil! That's a great question that we should probably do a better job answering as a community. I think it depends on how Flipkart wants to position itself wrt the HBase community. If you want to "just use" HBase, our recommendation, AFAIK, is to use whatever version our "stable" pointer is at. This should be a version that we as a community believe has the right balance of features and production use burn-in to work for a majority of HBase use cases. It also should keep you on a line of releases that we as a community are still providing bug fixes for around critical issues. It's always available at this location: http://www.apache.org/dist/hbase/stable/ Right now, that pointer is Apache HBase 1.4.9. The expectation, based on a few dev@hbase discussions over the last several months, is that when Apache HBase 1.5.0 comes out we'll update the stable pointer to it. That RC is scheduled to close at the end of this week. Ideally, upgrading along releases that have the stable pointer should be low risk. My current understanding is that when a feature proves sufficiently useful and unlikely to cause stabilization issues they'll get backported to a new HBase 1.y release and eventually the stable pointer will update to point at a release that includes it[1]. You should expect that it will take a long time or specific action on your part (backporting or testing) to get newer features if you deploy based on the stable releases. If you are planning to push the limits of HBase or if you are planning to leverage it as a critical piece of business infrastructure and you are planning to have an investment of folks working on it to match, you'll be able to better influence the direction of the project and leverage more aggressive or experimental improvements if you build around the set of HBase 2 releases. At the moment, that means either the latest Apache HBase 2.1.z if you need something in the next month, or Apache HBase 2.2.0 if you either want to directly participate in that release's vetting or you can wait until it is out. Note that so far the HBase community has expressly discussed and decided not to update the stable pointer to an HBase 2 release. You should expect that there will be operational difficulties that require gaining a deep understanding of internals[2] (which we as a community would love to help out with) if you deploy based on newer-than-stable releases. A brief aside to your earlier question about where releases are still happening; specifically there still being 1.2 releases. I'm the release manager for the 1.2 release line. Since it was the previous stable release line (for 1.2.0 - 1.2.6) I offered to continue making releases for ~6 months after we updated the stable pointer to a 1.4 release. I thought this provided a good-enough buffer for folks who need to plan and execute upgrading. Each 1.2.z release announcement starting with 1.2.7 has carried a message that said some version of "you should upgrade to the stable pointer which is currently 1.4.x". [1]: dev@hbase thread "[DISCUSS] No more release branches for 1.x, release from branch-1 directly" https://s.apache.org/shSE [2]: dev@hbase thread "[DISCUSS] Moving towards a branch-2 line that can get the 'stable' pointer." https://s.apache.org/STA2 HBASE-21745 On Mon, Mar 4, 2019 at 9:38 AM Nikhil Bafna wrote: > > So, are there any 1.x branches that are continuing to get new features? > > Looking at a 6 month view, should we (Flipkart) rather plan to develop (and > start contributing) on 2.x branch, instead of 1.x branches? > > > -- > Nikhil Bafna | 8095234263 > > > On Fri, Mar 1, 2019 at 4:43 PM Peter Somogyi wrote: > > > The current plan is to retire 2.0. The voting is in progress for 2.0.5 and > > more releases are not planned unless critical bugs are discovered. > > > > On the 1.3 line there was a discussion for EOL, but the Francis (RM) would > > like to continue that. > > > > HBase 1.5.0 is coming up shortly and you could also expect more bugfix > > releases on 1.2. > > > > On Thu, Feb 28, 2019 at 6:38 AM Nikhil Bafna wrote: > > > > > We run Hbase 1.2.x in our production that has a set of patches & > > backports. > > > > > > In the mailing list, I see discussions for EOL of 1.3 & 2.0.x. In another > > > mailing list discussion, it was pointed out that "... targeting only bug > > > fixes for branch-1, as version 1 approaches EOL" > > > > > > But, I see new releases happening on 1.2.x versions - which seems to be > > > contradictory. > > > > > > What are the EOL plans for the active versions? > > > > >
[jira] [Created] (HBASE-21997) Fix hbase-rest findbugs ST_WRITE_TO_STATIC_FROM_INSTANCE_METHOD complaint
stack created HBASE-21997: - Summary: Fix hbase-rest findbugs ST_WRITE_TO_STATIC_FROM_INSTANCE_METHOD complaint Key: HBASE-21997 URL: https://issues.apache.org/jira/browse/HBASE-21997 Project: HBase Issue Type: Sub-task Components: REST Reporter: stack Let me add annotations flagging the problem spot with annotations. It was already flagged 'hack' for test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Branch-2.0: EOL and a 2.0.5RC
Did as you described. Removed Master WALs, restarted, still getting 80% of my regions stuck. I will keep playing a bit but I think I will "just" upgrade to the last 2.2 and retry... Right now 2.0.4 seems a bit unstable for me :( Le sam. 16 févr. 2019 à 01:38, Stack a écrit : > Remove the Master WALs at least. The beta is damaged. > > If testing, trying to help out, I'd suggest move to branch-2.2. It is the > next minor release. 2.1.x has had some love and is in a good state. It is > superior to 2.0.x which we are trying to EOL (too many branches) so your > time would be better spent elsewhere. > > Thanks for the help JMS, > S > > > On Wed, Feb 13, 2019 at 5:03 AM Jean-Marc Spaggiari < > jean-m...@spaggiari.org> > wrote: > > > Hi Stack, > > > > Thanks for looking at it. So what's next? Do you want to me try to put > the > > latest 2.1 RC on top of it and see if it behaves well? Or just remove the > > Master WALs and stay on 2.0.4 to try the 2.2 upgrade path? I don' thave > an > > urgent need of this cluster, so I can play a bit with it if it helps. > > > > Any JIRA that I should open or update based on that? > > > > JMS > > > > Le lun. 11 févr. 2019 à 21:16, Stack a écrit : > > > > > Took a quick look. > > > > > > On startup, it has hundreds of AMv2 WALs to recover. Its backed up > unable > > > to let go of the early files because some old procedures have not > > > 'completed'.. This sort of backup problem has been addressed in later > > > hbase-2.0s. > > > > > > (Looks like oldest WAL is hdfs:// > > > > > > node2.distparser.com:8020/hbase/MasterProcWALs/pv2-0016.log > > > ) > > > > > > It then finds corrupt procedures which is probably why we are retaining > > > logs in first place. Corruption was fixed in later hbase-2.0s (may be a > > new > > > instance of corruption raising its head on master branch... but that > > > doesn't apply here). > > > > > > There is then an issue assigning namespace -- it has a mangled hostname > > -- > > > which is probably why the fail... Would be interesting if we saw > similar > > in > > > a later hbase... but probably a result of the mess above. > > > > > > Thanks for letting me take a look JMS. > > > > > > S > > > > > > > > > > > > On Mon, Feb 11, 2019 at 4:24 PM Jean-Marc Spaggiari < > > > jean-m...@spaggiari.org> > > > wrote: > > > > > > > Doesn't seems to work very well. > > > > > > > > Can you try this one? > > > > > > > > > > > > > > > > > > https://drive.google.com/file/d/1PMqJz4LjkEx0U2jYVVSLXaSEqcdHq7w4/view?usp=sharing > > > > > > > > JMS > > > > > > > > Le lun. 11 févr. 2019 à 16:27, Stack a écrit : > > > > > > > > > On Fri, Feb 8, 2019 at 11:47 AM Jean-Marc Spaggiari < > > > > > jean-m...@spaggiari.org> > > > > > wrote: > > > > > > > > > > > Probably not the best way to host a file, but logs are there: > > > > > > https://pastebin.com/dl/JaETSZfh > > > > > > I had a running 2.0.0-beta but 2.0.4 can't start. > > > > > > Let me know if you can't see the file (.tar.bz2) and I will try > > > > something > > > > > > different. > > > > > > JMS > > > > > > > > > > > > > > > > > Says "Your request is blocked due to invalid referrer. If you are > > > trying > > > > to > > > > > hotlink this page, please use: https://pastebin.com/raw/JaETSZfh;. > > > > > > > > > > I'm doing something wrong? > > > > > > > > > > Thanks JMS, > > > > > S > > > > > > > > > > > > > > > > Le ven. 8 févr. 2019 à 14:15, Stack a écrit : > > > > > > > > > > > > > On Wed, Feb 6, 2019 at 1:42 PM Jean-Marc Spaggiari < > > > > > > > jean-m...@spaggiari.org> > > > > > > > wrote: > > > > > > > > > > > > > > > Quick question here. Just upgraded from 2.0.0 BETA 2 to 2.0.4 > > and > > > > I'm > > > > > > > > having some issues to start HBase. I will probably be able to > > fix > > > > > that, > > > > > > > but > > > > > > > > I'm wondering if you want me to document those issues or if > > 2.0.x > > > > is > > > > > > too > > > > > > > > old so it's not needed? > > > > > > > > > > > > > > > > > > > > > > > Hey JMS. > > > > > > > > > > > > > > Would be interested in the issues you are seeing. Perhaps they > > > > pertain > > > > > to > > > > > > > branch-2.1+? > > > > > > > > > > > > > > Thanks, > > > > > > > S > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Le lun. 4 févr. 2019 à 21:11, 张铎(Duo Zhang) < > > > palomino...@gmail.com > > > > > > > > > > a > > > > > > > > écrit : > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > Andrew Purtell 于2019年2月5日周二 > 上午3:24写道： > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Feb 4, 2019 at 10:29 AM Stack > > > > wrote: > > > > > > > > > > > > > > > > > > > > > I was going to put up a 2.0.5 RC to address > > > > > > > > > > > https://issues.apache.org/jira/browse/HBASE-21791.Its > > been > > > > > > about a > > > > > > > > > month > > > > > > > > > > > since 2.0.4. There are 50 odd fixes in 2.0.5 currently > > [1] > > > > > mostly > > > > > > > > > > >
Re: Release 2.2.0
Bump ;) Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari a écrit : > Hi all, > > When we will have a 2.2.0 RC I will give a try of the upgrade path from > 2.0.x... do we have any idea when this will be out? > > JMS > > Le mar. 29 janv. 2019 02 h 09, Guanghao Zhang a > écrit : > >> Cut a new branch-2.2 at this commit. >> >> commit e736d78362253936492fb3bd16e614d14859281d >> Author: Duo Zhang >> Date: Mon Jan 28 18:21:51 2019 +0800 >> >> HBASE-21792 Mark HTableMultiplexer as deprecated and remove it in 3.0.0 >> >> Signed-off-by: Michael Stack >> >> Sean Busbey 于2019年1月24日周四 上午9:45写道： >> >> > Okay it sounds like we definitely need a better doc about this as a >> > starting point. I have some additional questions about failure handling; >> > should we go through them here or in a jira about improving how upgrade >> > from 2.0/2.1 gets handled? >> > >> > On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) > > >> > > Oh, you misunderstood me. It is just for master, you need make sure >> that >> > > before you killing the old version master, there is no RITs. And once >> the >> > > new master is up, everything is fine., as the new master will detect >> if >> > > there are old style AssignProcedure/UnassignProcedures, if so it will >> > quit >> > > immediately. >> > > >> > > Sean Busbey 于2019年1月23日周三 下午9:21写道： >> > > >> > > > Yes, please. I don't think it's reasonable to expect no region >> > > transitions >> > > > during a rolling upgrade window; that would imply no servers can >> crash >> > > > during the upgrade. >> > > > >> > > > On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang) > > wrote: >> > > > >> > > > > From 1.x it is OK, but from 2.0 or 2.1, we need make sure that >> there >> > > are >> > > > no >> > > > > RITs ongoing. We could see if we can make the upgrading more >> > smoothly. >> > > > > >> > > > > Guanghao Zhang 于2019年1月23日周三 下午8:56写道： >> > > > > >> > > > > > Our new internal branch is based on branch-2. And we already >> > rolling >> > > > > > upgrade our staging cluster from our internal 0.98 branch to >> it... >> > I >> > > > will >> > > > > > take a try for 2.0.* to 2.2.0. >> > > > > > >> > > > > > Are you saying we need to make sure it can do this? Or are you >> > > > > > > asserting that it already does? >> > > > > > > >> > > > > > It already does. >> > > > > > >> > > > > > >> > > > > > Sean Busbey 于2019年1月22日周二 下午9:48写道： >> > > > > > >> > > > > > > excellent! thanks for volunteering to get the 2.2 release line >> > > going >> > > > > > > Guanghao! >> > > > > > > >> > > > > > > > Need to add more document about how to rolling upgrade from >> > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how >> > rolling >> > > > > > upgrade >> > > > > > > from 1.* to 2.2.*. >> > > > > > > >> > > > > > > Has anyone confirmed that rolling upgrade to 2.2.0 works? I >> > thought >> > > > it >> > > > > > > couldn't because of the change to assignment handling classes? >> > > > > > > >> > > > > > > > Now HBCK2 tool support branch-2's region assignments, >> > > > > > > too. >> > > > > > > >> > > > > > > Are you saying we need to make sure it can do this? Or are you >> > > > > > > asserting that it already does? >> > > > > > > >> > > > > > > On Sun, Jan 20, 2019 at 10:25 PM Guanghao Zhang < >> > > zghao...@gmail.com> >> > > > > > > wrote: >> > > > > > > > >> > > > > > > > Hi, all, there has been six months since we released 2.1.0. >> And >> > > > there >> > > > > > are >> > > > > > > > 429 issues which fixed version is 2.2.0[1]. Our internal >> branch >> > > > which >> > > > > > > based >> > > > > > > > branch-2 run ITBLL successfully recently. branch-2 is stable >> > now >> > > > and >> > > > > it >> > > > > > > is >> > > > > > > > time to release 2.2.0. I volunteered to be the release >> manager >> > > for >> > > > > the >> > > > > > > 2.2 >> > > > > > > > release line. And plan to cut branch-2.2 from branch-2. >> > > > > > > > >> > > > > > > > For 2.2.0, the biggest change is about AMV2[2]: HBASE-20881 >> is >> > an >> > > > > > > > incompatible change and different implemenation with >> branch-2.0 >> > > and >> > > > > > > > branch-2.1. Need to add more document about how to rolling >> > > upgrade >> > > > > from >> > > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how >> > > rolling >> > > > > > > upgrade >> > > > > > > > from 1.* to 2.2.*. Now HBCK2 tool support branch-2's region >> > > > > > assignments, >> > > > > > > > too. >> > > > > > > > >> > > > > > > > Another features will be included: >> > > > > > > > 1. HBASE-20610 Procedure V2 - Distributed Log Splitting[3] >> > > > > > > > 2. HBASE-21649 Complete Thrift2[4] >> > > > > > > > 3. HBASE-16707 Improve throttling feature for production >> > usage[5] >> > > > > > > > 4. HBASE-20886 [Auth] Support keytab login in hbase >> client[6] >> > > > > > > > 5. HBASE-20636 Introduce two bloom filter type : >> > > > > ROWPREFIX_FIXED_LENGTH >> > > > > > > and >> > > > > > > > ROWPREFIX_DELIMITED[7] >> > > > > > > > >> > > > > > > >
Re: Request for an invite to Slack Channel
I've sent an invite to you, Dmitriy. On Tue, Mar 5, 2019 at 9:47 AM Dmitriy Kuharev < dmitriy.kuha...@ultratendency.com> wrote: > Hello, > > I would like to join the discussion in your slack channel. I have a few > questions about submitting changes. > > Best Regards, > Dmitriy. >
Re: Release 2.2.0
I believe work on the RC is being tracked in https://issues.apache.org/jira/browse/HBASE-21747 Looks like an RC is imminent. On Tue, Mar 5, 2019, 14:39 Jean-Marc Spaggiari wrote: > Bump ;) > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari > > a écrit : > > > Hi all, > > > > When we will have a 2.2.0 RC I will give a try of the upgrade path from > > 2.0.x... do we have any idea when this will be out? > > > > JMS > > > > Le mar. 29 janv. 2019 02 h 09, Guanghao Zhang a > > écrit : > > > >> Cut a new branch-2.2 at this commit. > >> > >> commit e736d78362253936492fb3bd16e614d14859281d > >> Author: Duo Zhang > >> Date: Mon Jan 28 18:21:51 2019 +0800 > >> > >> HBASE-21792 Mark HTableMultiplexer as deprecated and remove it in 3.0.0 > >> > >> Signed-off-by: Michael Stack > >> > >> Sean Busbey 于2019年1月24日周四 上午9:45写道： > >> > >> > Okay it sounds like we definitely need a better doc about this as a > >> > starting point. I have some additional questions about failure > handling; > >> > should we go through them here or in a jira about improving how > upgrade > >> > from 2.0/2.1 gets handled? > >> > > >> > On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) wrote: > >> > > >> > > Oh, you misunderstood me. It is just for master, you need make sure > >> that > >> > > before you killing the old version master, there is no RITs. And > once > >> the > >> > > new master is up, everything is fine., as the new master will detect > >> if > >> > > there are old style AssignProcedure/UnassignProcedures, if so it > will > >> > quit > >> > > immediately. > >> > > > >> > > Sean Busbey 于2019年1月23日周三 下午9:21写道： > >> > > > >> > > > Yes, please. I don't think it's reasonable to expect no region > >> > > transitions > >> > > > during a rolling upgrade window; that would imply no servers can > >> crash > >> > > > during the upgrade. > >> > > > > >> > > > On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang) >> > wrote: > >> > > > > >> > > > > From 1.x it is OK, but from 2.0 or 2.1, we need make sure that > >> there > >> > > are > >> > > > no > >> > > > > RITs ongoing. We could see if we can make the upgrading more > >> > smoothly. > >> > > > > > >> > > > > Guanghao Zhang 于2019年1月23日周三 下午8:56写道： > >> > > > > > >> > > > > > Our new internal branch is based on branch-2. And we already > >> > rolling > >> > > > > > upgrade our staging cluster from our internal 0.98 branch to > >> it... > >> > I > >> > > > will > >> > > > > > take a try for 2.0.* to 2.2.0. > >> > > > > > > >> > > > > > Are you saying we need to make sure it can do this? Or are you > >> > > > > > > asserting that it already does? > >> > > > > > > > >> > > > > > It already does. > >> > > > > > > >> > > > > > > >> > > > > > Sean Busbey 于2019年1月22日周二 下午9:48写道： > >> > > > > > > >> > > > > > > excellent! thanks for volunteering to get the 2.2 release > line > >> > > going > >> > > > > > > Guanghao! > >> > > > > > > > >> > > > > > > > Need to add more document about how to rolling upgrade > from > >> > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how > >> > rolling > >> > > > > > upgrade > >> > > > > > > from 1.* to 2.2.*. > >> > > > > > > > >> > > > > > > Has anyone confirmed that rolling upgrade to 2.2.0 works? I > >> > thought > >> > > > it > >> > > > > > > couldn't because of the change to assignment handling > classes? > >> > > > > > > > >> > > > > > > > Now HBCK2 tool support branch-2's region assignments, > >> > > > > > > too. > >> > > > > > > > >> > > > > > > Are you saying we need to make sure it can do this? Or are > you > >> > > > > > > asserting that it already does? > >> > > > > > > > >> > > > > > > On Sun, Jan 20, 2019 at 10:25 PM Guanghao Zhang < > >> > > zghao...@gmail.com> > >> > > > > > > wrote: > >> > > > > > > > > >> > > > > > > > Hi, all, there has been six months since we released > 2.1.0. > >> And > >> > > > there > >> > > > > > are > >> > > > > > > > 429 issues which fixed version is 2.2.0[1]. Our internal > >> branch > >> > > > which > >> > > > > > > based > >> > > > > > > > branch-2 run ITBLL successfully recently. branch-2 is > stable > >> > now > >> > > > and > >> > > > > it > >> > > > > > > is > >> > > > > > > > time to release 2.2.0. I volunteered to be the release > >> manager > >> > > for > >> > > > > the > >> > > > > > > 2.2 > >> > > > > > > > release line. And plan to cut branch-2.2 from branch-2. > >> > > > > > > > > >> > > > > > > > For 2.2.0, the biggest change is about AMV2[2]: > HBASE-20881 > >> is > >> > an > >> > > > > > > > incompatible change and different implemenation with > >> branch-2.0 > >> > > and > >> > > > > > > > branch-2.1. Need to add more document about how to rolling > >> > > upgrade > >> > > > > from > >> > > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about > how > >> > > rolling > >> > > > > > > upgrade > >> > > > > > > > from 1.* to 2.2.*. Now HBCK2 tool support branch-2's > region > >> > > > > > assignments, > >> > > > > > > > too. > >> > > > > > > > > >> > > > > > > > Another features will
Re: Release 2.2.0
Yes, Guanghao is still working on it. It usually spends more time for a minor release than a patch release, as we need to align the git commits and the jira issues. And usually there will be a lot of differences... Sean Busbey 于2019年3月6日周三 上午9:40写道： > I believe work on the RC is being tracked in > > https://issues.apache.org/jira/browse/HBASE-21747 > > Looks like an RC is imminent. > > On Tue, Mar 5, 2019, 14:39 Jean-Marc Spaggiari > wrote: > > > Bump ;) > > > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari < > jean-m...@spaggiari.org > > > > > a écrit : > > > > > Hi all, > > > > > > When we will have a 2.2.0 RC I will give a try of the upgrade path from > > > 2.0.x... do we have any idea when this will be out? > > > > > > JMS > > > > > > Le mar. 29 janv. 2019 02 h 09, Guanghao Zhang a > > > écrit : > > > > > >> Cut a new branch-2.2 at this commit. > > >> > > >> commit e736d78362253936492fb3bd16e614d14859281d > > >> Author: Duo Zhang > > >> Date: Mon Jan 28 18:21:51 2019 +0800 > > >> > > >> HBASE-21792 Mark HTableMultiplexer as deprecated and remove it in > 3.0.0 > > >> > > >> Signed-off-by: Michael Stack > > >> > > >> Sean Busbey 于2019年1月24日周四 上午9:45写道： > > >> > > >> > Okay it sounds like we definitely need a better doc about this as a > > >> > starting point. I have some additional questions about failure > > handling; > > >> > should we go through them here or in a jira about improving how > > upgrade > > >> > from 2.0/2.1 gets handled? > > >> > > > >> > On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) > wrote: > > >> > > > >> > > Oh, you misunderstood me. It is just for master, you need make > sure > > >> that > > >> > > before you killing the old version master, there is no RITs. And > > once > > >> the > > >> > > new master is up, everything is fine., as the new master will > detect > > >> if > > >> > > there are old style AssignProcedure/UnassignProcedures, if so it > > will > > >> > quit > > >> > > immediately. > > >> > > > > >> > > Sean Busbey 于2019年1月23日周三 下午9:21写道： > > >> > > > > >> > > > Yes, please. I don't think it's reasonable to expect no region > > >> > > transitions > > >> > > > during a rolling upgrade window; that would imply no servers can > > >> crash > > >> > > > during the upgrade. > > >> > > > > > >> > > > On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang) < > palomino...@gmail.com > > >> > wrote: > > >> > > > > > >> > > > > From 1.x it is OK, but from 2.0 or 2.1, we need make sure that > > >> there > > >> > > are > > >> > > > no > > >> > > > > RITs ongoing. We could see if we can make the upgrading more > > >> > smoothly. > > >> > > > > > > >> > > > > Guanghao Zhang 于2019年1月23日周三 下午8:56写道： > > >> > > > > > > >> > > > > > Our new internal branch is based on branch-2. And we already > > >> > rolling > > >> > > > > > upgrade our staging cluster from our internal 0.98 branch to > > >> it... > > >> > I > > >> > > > will > > >> > > > > > take a try for 2.0.* to 2.2.0. > > >> > > > > > > > >> > > > > > Are you saying we need to make sure it can do this? Or are > you > > >> > > > > > > asserting that it already does? > > >> > > > > > > > > >> > > > > > It already does. > > >> > > > > > > > >> > > > > > > > >> > > > > > Sean Busbey 于2019年1月22日周二 下午9:48写道： > > >> > > > > > > > >> > > > > > > excellent! thanks for volunteering to get the 2.2 release > > line > > >> > > going > > >> > > > > > > Guanghao! > > >> > > > > > > > > >> > > > > > > > Need to add more document about how to rolling upgrade > > from > > >> > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about > how > > >> > rolling > > >> > > > > > upgrade > > >> > > > > > > from 1.* to 2.2.*. > > >> > > > > > > > > >> > > > > > > Has anyone confirmed that rolling upgrade to 2.2.0 works? > I > > >> > thought > > >> > > > it > > >> > > > > > > couldn't because of the change to assignment handling > > classes? > > >> > > > > > > > > >> > > > > > > > Now HBCK2 tool support branch-2's region assignments, > > >> > > > > > > too. > > >> > > > > > > > > >> > > > > > > Are you saying we need to make sure it can do this? Or are > > you > > >> > > > > > > asserting that it already does? > > >> > > > > > > > > >> > > > > > > On Sun, Jan 20, 2019 at 10:25 PM Guanghao Zhang < > > >> > > zghao...@gmail.com> > > >> > > > > > > wrote: > > >> > > > > > > > > > >> > > > > > > > Hi, all, there has been six months since we released > > 2.1.0. > > >> And > > >> > > > there > > >> > > > > > are > > >> > > > > > > > 429 issues which fixed version is 2.2.0[1]. Our internal > > >> branch > > >> > > > which > > >> > > > > > > based > > >> > > > > > > > branch-2 run ITBLL successfully recently. branch-2 is > > stable > > >> > now > > >> > > > and > > >> > > > > it > > >> > > > > > > is > > >> > > > > > > > time to release 2.2.0. I volunteered to be the release > > >> manager > > >> > > for > > >> > > > > the > > >> > > > > > > 2.2 > > >> > > > > > > > release line. And plan to cut branch-2.2 from branch-2. > > >> > > > > > > > > > >> > > > > > > >
[jira] [Resolved] (HBASE-21998) Move branch-2.1 version from 2.1.4 to 2.1.5-SNAPSHOT
[ https://issues.apache.org/jira/browse/HBASE-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21998. --- Resolution: Fixed Fix Version/s: 2.1.4 Pushed to branch-2.1. > Move branch-2.1 version from 2.1.4 to 2.1.5-SNAPSHOT > > > Key: HBASE-21998 > URL: https://issues.apache.org/jira/browse/HBASE-21998 > Project: HBase > Issue Type: Sub-task > Components: rm >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.1.4 > > > Moving on the version. If we have to make a new RC, the new rm scripts know > how to deal w/ a version gone too far. The new rm scripts expect the version > to have been moved on (this is what they do when they are running the > versioning and tagging of the candidate). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
