A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Phil Yang
Nice article! Thanks for the authors. An off-the-topic suggestion to dev list: Now we commit some big and new features to master branch only, which will be included in a new major version, for example, 2.0. However, a major version is not upgraded very quickly, 1.0.0 was released two years ago an

[jira] [Created] (HBASE-17763) IPCUtil.wrapException will wrap DoNotRetryIOException with IOException

2017-03-09 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-17763: - Summary: IPCUtil.wrapException will wrap DoNotRetryIOException with IOException Key: HBASE-17763 URL: https://issues.apache.org/jira/browse/HBASE-17763 Project: HBase

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Duo Zhang
Yeah we have put too much things into the 2.0 release. And I believe there is a release schedule for 2.0 in the mailing-list? 2017-03-09 16:34 GMT+08:00 Phil Yang : > Nice article! Thanks for the authors. > > An off-the-topic suggestion to dev list: > > Now we commit some big and new features to

Re: HDFS Balancer

2017-03-09 Thread Jean-Marc Spaggiari
So there is no way to use the pinning feature without having to use the favored nodes option? :( Le 2017-03-08 6:13 AM, "Harsh J" a écrit : > Hey Lars!, > > I was on a similar line of investigation today, and I've filed > https://issues.apache.org/jira/browse/HBASE-17760 to change the text. The

Successful: HBase Generate Website

2017-03-09 Thread Apache Jenkins Server
Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If yo

Re: What if I want to write another table in MasterObserver.preModifyColumnFamily ?

2017-03-09 Thread Xi Yang
Thank you Anoop. After thinking, I give up the idea about write records to RS, I will using other ways like zk, or just a text file. I appreciate your help! 2017-03-07 23:36 GMT-08:00 Anoop John : > It will be cross server call.. The pre/postModifyColumn is in master > side. (MasterObserver) You

[jira] [Reopened] (HBASE-17761) Test TestRemoveRegionMetrics.testMoveRegion fails intermittently because of race condition

2017-03-09 Thread Umesh Agashe (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-17761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe reopened HBASE-17761: -- Adding branch-1 patch > Test TestRemoveRegionMetrics.testMoveRegion fails intermittently because o

Re: [VOTE] Backup/Restore feature for HBase 2.0, vote closing 3/11/2017

2017-03-09 Thread Ted Yu
+1 from me as well. On Wed, Mar 8, 2017 at 3:48 PM, Enis Söztutar wrote: > Thanks Vladimir for the write up and the work. Glad to see progress. > > Here is my +1. I'm pretty sure we can get the blockers in before the 2.0 > timeframe with the momentum, so it is a good idea to merge now so that >

Re: [VOTE] Backup/Restore feature for HBase 2.0, vote closing 3/11/2017

2017-03-09 Thread Vladimir Rodionov
bump On Wed, Mar 8, 2017 at 3:52 PM, Vladimir Rodionov wrote: > No problem, we can extend deadline. > > On Wed, Mar 8, 2017 at 3:31 PM, Ted Yu wrote: > >> March 11th is on weekend. >> >> Do you want to give people who haven't looked at the mega patch in depth >> some more time ? >> >> Cheers >>

Re: What if I want to write another table in MasterObserver.preModifyColumnFamily ?

2017-03-09 Thread Ted Yu
Zookeeper is supposed to store transient data. Plus you need to secure the audit log in zookeeper so that unauthorized user cannot temper the audit. On Thu, Mar 9, 2017 at 9:24 AM, Xi Yang wrote: > Thank you Anoop. After thinking, I give up the idea about write records to > RS, I will using othe

[jira] [Created] (HBASE-17764) Solve TestMultiSlaveReplication flakiness

2017-03-09 Thread Stephen Yuan Jiang (JIRA)
Stephen Yuan Jiang created HBASE-17764: -- Summary: Solve TestMultiSlaveReplication flakiness Key: HBASE-17764 URL: https://issues.apache.org/jira/browse/HBASE-17764 Project: HBase Issue

[jira] [Created] (HBASE-17765) Reviving the merge possibility in the CompactingMemStore

2017-03-09 Thread Anastasia Braginsky (JIRA)
Anastasia Braginsky created HBASE-17765: --- Summary: Reviving the merge possibility in the CompactingMemStore Key: HBASE-17765 URL: https://issues.apache.org/jira/browse/HBASE-17765 Project: HBase

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Stack
On Thu, Mar 9, 2017 at 12:34 AM, Phil Yang wrote: > > > So my suggestion is cutting branch-x faster and have some fixed period, for > example, six month or one year? > You are right Phil. The Release Managers for the minor releases have been doing a good job keeping up a decent release cadence

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Andrew Purtell
The only way forward for saving 2.0 at this point is to *make the branch and spin the RC. *Just do it. Kick out by revert what obviously isn't ready. Solicit help in getting partially finished things into working state. Kick them out too if the help does not arrive. Maybe too much is in a half don

[jira] [Created] (HBASE-17766) Generate Javadoc for hbase-spark module

2017-03-09 Thread Yi Liang (JIRA)
Yi Liang created HBASE-17766: Summary: Generate Javadoc for hbase-spark module Key: HBASE-17766 URL: https://issues.apache.org/jira/browse/HBASE-17766 Project: HBase Issue Type: Bug

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Ashu Pachauri
In my opinion, a major release is based on two simultaneous decisions: 1. Is it time; may be a year is a good time frame? (It's useless accumulating too much code that is not battle tested and then expect people to deploy it to production without experiencing a plethora of issues.) 2. Is there at

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Stephen Jiang
I don't see a point to have branch-2 from branch-1. For customer/users, we always can have a 1.x release to give them all the features they want from branch-1. My understand is that one of the difference of major release and minor release is that major release could break some backward compatibil

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Andrew Purtell
Oh, I don't know. I may never be comfortable with a backport of MOB into branch-1, but a branch-2 including it would be fine. And my point is not that making a branch-2 out of branch-1 is desirable, simply that it could be the most practical way forward if we are stuck on master with too much unfi

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Andrew Purtell
> For 2.0 release or future major release, what we need is planning - THEME ​> ​ (what is the biggest excitement for the release) and MUST-HAVE FEATURES. ​> ​ All must-have features should have an owner and some estimate of completing ​> ​ time. ​With all due respect, this is just talk. Appeals to

branch-2

2017-03-09 Thread Ted Yu
Hi, I was wondering why there is branch-2 ? https://github.com/apache/hbase/tree/branch-2 As far as I know, there is no consensus on when branch-2 should be created. Thanks

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Mikhail Antonov
>>"The only way forward for saving 2.0 at this point is to *make the branch and spin the RC." big +1 to that. I do also think that talking about planning in the context of open-source community development is a bit hard - there's no planning but what people do. If we release regularly, however, w

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Duo Zhang
Let's just cut branch-2 ASAP and set a deadline for the partially-completed features? 2017-03-10 9:29 GMT+08:00 Mikhail Antonov : > >>"The only way forward for saving 2.0 at this point is to *make the branch > and spin the RC." > > big +1 to that. > > I do also think that talking about planning i

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Mikhail Antonov
To rephrase myself - I think we shouldn't be taking stance that MajorBranchX can't be released until features f1, f2, f2,...fN are all completed. That's just not going to fly. There will always be features suddenly way more complicated than they appeared, features that don't have enough manpower b

[jira] [Resolved] (HBASE-11033) Allow test-patch.sh to run selected test(s) if patch contains changes to test classes only

2017-03-09 Thread Ted Yu (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-11033. Resolution: Won't Fix > Allow test-patch.sh to run selected test(s) if patch contains changes to test > cl

Re: A suggestion for releasing major versions faster (Was: NOTICE: Nice testimony on benefits of the offheap read-path work now up on our blog)

2017-03-09 Thread Phil Yang
> To rephrase myself - I think we shouldn't be taking stance that > MajorBranchX can't be released until features f1, f2, f2,...fN are all completed. Agree, we should not be blocked by any feature. Some new features don't conflict with current codes, I think we can just commit to branches and add

[jira] [Created] (HBASE-17767) hbase CMS gc pause program

2017-03-09 Thread gehaijiang (JIRA)
gehaijiang created HBASE-17767: -- Summary: hbase CMS gc pause program Key: HBASE-17767 URL: https://issues.apache.org/jira/browse/HBASE-17767 Project: HBase Issue Type: Bug Affects Versions

Re: Moving 2.0 forward

2017-03-09 Thread Stack
On Tue, Mar 7, 2017 at 1:51 PM, Josh Elser wrote: > Thanks for pulling in the FS Quotas work, Stack. I'm trying to cross the > last T's and dot the last I's. > > The biggest thing I know I need to do still is to write a new chapter to > the book. After that, I'd start entertaining larger reviews/

Re: Moving 2.0 forward

2017-03-09 Thread Stack
On Wed, Mar 8, 2017 at 4:06 PM, Jerry He wrote: > Thanks for the write-up, Stack. > > I take the liberty to make the Spark item as: > > 4.3 hbase-spark > ktczrlKHK8N4SZzs/edit#heading=h.24l014zh4tmp> > > 4.3.1 Status= >

[jira] [Resolved] (HBASE-17767) hbase CMS gc pause program

2017-03-09 Thread Duo Zhang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-17767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-17767. --- Resolution: Invalid > hbase CMS gc pause program > > >

Re: [VOTE] Backup/Restore feature for HBase 2.0, vote closing 3/11/2017

2017-03-09 Thread Vladimir Rodionov
bump On Thu, Mar 9, 2017 at 10:11 AM, Ted Yu wrote: > +1 from me as well. > > On Wed, Mar 8, 2017 at 3:48 PM, Enis Söztutar wrote: > > > Thanks Vladimir for the write up and the work. Glad to see progress. > > > > Here is my +1. I'm pretty sure we can get the blockers in before the 2.0 > > time