Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

Here is my +1. Executed the test suites several times, with -Dsurefire.secondPartForkCount=1, and also the exclusion of flakey tests(including TestFromClientSide) I could get a successful build. Started two clusters with the code of the latest HBASE-19397, tried adding a new peer, it worked

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

On Sun, Jan 7, 2018 at 3:14 AM, Jean-Marc Spaggiari wrote: > Ok, thanks Stack. I will keep it running all day long until I get a > successful one. Is that useful that I report all the failed? Or just a wast > of time? Here is the last failed: > > [INFO] Results: >

[jira] [Created] (HBASE-19731) TestFromClientSide#testCheckAndDeleteWithCompareOp and testNullQualifier are flakey

stack created HBASE-19731: - Summary: TestFromClientSide#testCheckAndDeleteWithCompareOp and testNullQualifier are flakey Key: HBASE-19731 URL: https://issues.apache.org/jira/browse/HBASE-19731 Project: HBase

[jira] [Created] (HBASE-19730) Backport HBASE-14497 Reverse Scan threw StackOverflow caused by readPt checking

Ted Yu created HBASE-19730: -- Summary: Backport HBASE-14497 Reverse Scan threw StackOverflow caused by readPt checking Key: HBASE-19730 URL: https://issues.apache.org/jira/browse/HBASE-19730 Project: HBase

[jira] [Created] (HBASE-19729) Optimize UserScanQueryMatcher#mergeFilterResponse

Zheng Hu created HBASE-19729: Summary: Optimize UserScanQueryMatcher#mergeFilterResponse Key: HBASE-19729 URL: https://issues.apache.org/jira/browse/HBASE-19729 Project: HBase Issue Type: Bug

[jira] [Resolved] (HBASE-19358) Improve the stability of splitting log when do fail over

[ https://issues.apache.org/jira/browse/HBASE-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Li resolved HBASE-19358. --- Resolution: Fixed Hadoop Flags: Reviewed Release Note: After HBASE-19358 we introduced a new

[jira] [Resolved] (HBASE-19727) RS keeps calling reportForDuty to backup HMaster and can not online properly

[ https://issues.apache.org/jira/browse/HBASE-19727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-19727. --- Resolution: Invalid Probably because I've been using a problematic zookeeper. Close a Invalid for

[jira] [Created] (HBASE-19728) Add lock to filesCompacting in all place.

binlijin created HBASE-19728: Summary: Add lock to filesCompacting in all place. Key: HBASE-19728 URL: https://issues.apache.org/jira/browse/HBASE-19728 Project: HBase Issue Type: Bug

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Hope we still have time to get the procedure based replication peer modification(HBASE-19397) in before cutting branch-2.0... :( 2018-01-07 21:51 GMT+08:00 Stack : > On Sun, Jan 7, 2018 at 12:55 AM, Apekshit Sharma > wrote: > > > bq. Don't you think we have

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

On Sun, Jan 7, 2018 at 12:55 AM, Apekshit Sharma wrote: > bq. Don't you think we have enough branches already mighty Appy? > Yeah we do...sigh. > > > idk about that. But don't we need a *patch* branch branch-2.0 (just like > branch-1.4) where we "make backwards-compatible bug

[jira] [Created] (HBASE-19727) RS keeps calling reportForDuty to backup HMaster and can not start properly

Duo Zhang created HBASE-19727: - Summary: RS keeps calling reportForDuty to backup HMaster and can not start properly Key: HBASE-19727 URL: https://issues.apache.org/jira/browse/HBASE-19727 Project: HBase

[jira] [Created] (HBASE-19726) Failed to start HMaster due to infinite retrying on meta assign

Duo Zhang created HBASE-19726: - Summary: Failed to start HMaster due to infinite retrying on meta assign Key: HBASE-19726 URL: https://issues.apache.org/jira/browse/HBASE-19726 Project: HBase

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Excellent! Thanks again! Starting again with the tests... JMS 2018-01-07 8:04 GMT-05:00 张铎(Duo Zhang) : > The last '-fn' option in the mvn command does that magic for you. > > 2018-01-07 19:03 GMT+08:00 Jean-Marc Spaggiari : > > > So that's the

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

The last '-fn' option in the mvn command does that magic for you. 2018-01-07 19:03 GMT+08:00 Jean-Marc Spaggiari : > So that's the way! Super. Thanks 张铎. Last, is there a way to keep going > with the remaining tests even if we get a failure on a test? > > JMS > >

[jira] [Created] (HBASE-19725) Build fails, unable to read hbase/checkstyle-suppressions.xml "invalid distance too far back"

stack created HBASE-19725: - Summary: Build fails, unable to read hbase/checkstyle-suppressions.xml "invalid distance too far back" Key: HBASE-19725 URL: https://issues.apache.org/jira/browse/HBASE-19725

[jira] [Created] (HBASE-19724) Fix Checkstyle errors in hbase-hadoop2-compat

Jan Hentschel created HBASE-19724: - Summary: Fix Checkstyle errors in hbase-hadoop2-compat Key: HBASE-19724 URL: https://issues.apache.org/jira/browse/HBASE-19724 Project: HBase Issue Type:

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

So that's the way! Super. Thanks 张铎. Last, is there a way to keep going with the remaining tests even if we get a failure on a test? JMS 2018-01-07 5:56 GMT-05:00 张铎(Duo Zhang) : > You can try to copy the command line from the pre commit job where we will > bypass the

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

You can try to copy the command line from the pre commit job where we will bypass the flakey tests... This is the command I use to run UTs mvn -PrunAllTests

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Ok, thanks Stack. I will keep it running all day long until I get a successful one. Is that useful that I report all the failed? Or just a wast of time? Here is the last failed: [INFO] Results: [INFO] [ERROR] Failures: [ERROR] TestFromClientSide.testCheckAndDeleteWithCompareOp:4982 expected: