[jira] [Resolved] (HBASE-24895) Speed up TestFromClientSide3 by reduce the table regions number

2020-08-19 Thread Guanghao Zhang (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24895.

Fix Version/s: 2.2.6
   Resolution: Fixed

> Speed up TestFromClientSide3 by reduce the table regions number
> ---
>
> Key: HBASE-24895
> URL: https://issues.apache.org/jira/browse/HBASE-24895
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.6
>
>
> [https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/52/testReport/junit/org.apache.hadoop.hbase.client/TestFromClientSide3//]
>  
> |[testHTableExistsMethodMultipleRegionsMultipleGets|https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/52/testReport/junit/org.apache.hadoop.hbase.client/TestFromClientSide3//testHTableExistsMethodMultipleRegionsMultipleGets]|2
>  min 58 sec|Regression|
> |[testHTableExistsMethodMultipleRegionsSingleGet|https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/52/testReport/junit/org.apache.hadoop.hbase.client/TestFromClientSide3//testHTableExistsMethodMultipleRegionsSingleGet]|4
>  min 20 sec|Passed|
>  
> It take too many time and timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24912) Enalrge MemstoreFlusherChore/CompactionChecker period for unit test

2020-08-19 Thread Guanghao Zhang (Jira)
Guanghao Zhang created HBASE-24912:
--

 Summary: Enalrge MemstoreFlusherChore/CompactionChecker period for 
unit test
 Key: HBASE-24912
 URL: https://issues.apache.org/jira/browse/HBASE-24912
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang


Too many debug logs when run unit test now.

 

2020-08-19 01:20:59,899 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): CompactionChecker execution time: 0 ms.
2020-08-19 01:20:59,899 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): MemstoreFlusherChore execution time: 0 ms.
2020-08-19 01:20:59,900 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): CompactionChecker execution time: 0 ms.
2020-08-19 01:20:59,900 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): MemstoreFlusherChore execution time: 0 ms.
2020-08-19 01:20:59,905 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): MemstoreFlusherChore execution time: 0 ms.
2020-08-19 01:20:59,905 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): CompactionChecker execution time: 0 ms.
2020-08-19 01:21:00,001 DEBUG [regionserver/asf909:0.Chore.1] 
hbase.ScheduledChore(192): CompactionChecker execution time: 0 ms.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24907) Turn off the balancer when test region admin api

2020-08-19 Thread Guanghao Zhang (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24907.

Fix Version/s: 2.2.6
   Resolution: Fixed

> Turn off the balancer when test region admin api
> 
>
> Key: HBASE-24907
> URL: https://issues.apache.org/jira/browse/HBASE-24907
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.6
>
>
> For region admin api, we will test move/split/merge/assign/unassign and test 
> the region location right or not. But the balancer may move region to other 
> places and break the UT. So turn off the balancer for TestAsyncRegionAdminApi.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Third release candidate for hbase-thirdparty 3.4.0 is available for download

2020-08-19 Thread Stack
+1

Added it to my hbase 2 pom. Built it. Checked a running instance. Loaded
and confirmed some data.

S

On Mon, Aug 17, 2020 at 1:04 AM 张铎(Duo Zhang)  wrote:

> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.4.0RC2
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase thirdparty 3.4.0
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 3.4.0RC2:
>
>   https://github.com/apache/hbase-thirdparty/tree/3.4.0RC2
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-3.4.0RC2/
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1405/
>
> Artifacts were signed with the 9AD2AE49 key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> We shade jetty and jersey in this version for addressing the conflicts
> between jetty 9.3 and 9.4, as hadoop recently upgraded its jetty from 9.3
> to 9.4 in patch releases.
>
> To learn more about Apache hbase thirdparty, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>


[jira] [Created] (HBASE-24911) Configure a max global timeout for HMaster to wait for RS to check in

2020-08-19 Thread Sandeep Guggilam (Jira)
Sandeep Guggilam created HBASE-24911:


 Summary: Configure a max global timeout for HMaster to wait for RS 
to check in
 Key: HBASE-24911
 URL: https://issues.apache.org/jira/browse/HBASE-24911
 Project: HBase
  Issue Type: Improvement
Reporter: Sandeep Guggilam
Assignee: Sandeep Guggilam


As part of the initialization process for active master, it waits for region 
servers to check in before completing the initialization. Currently it runs 
into a loop where it waits in the loop for ever when there are no region 
servers that are reported to it 
([https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java#L1126)]

 

We should probably have a global max timeout after which the master should give 
up and abort itself letting other masters to take over as active master . This 
is especially useful in the cases where the incoming connections to the master 
are not accepted because of network issue



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24837) Ignore... check what fails when zk-based WAL splitter enabled

2020-08-19 Thread Michael Stack (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Stack resolved HBASE-24837.
---
Resolution: Not A Problem

Tests passed. Old system seems to work still at least as according to our 
tests. Resolving as 'Not A Problem'.

> Ignore... check what fails when zk-based WAL splitter enabled
> -
>
> Key: HBASE-24837
> URL: https://issues.apache.org/jira/browse/HBASE-24837
> Project: HBase
>  Issue Type: Sub-task
>  Components: wal
>Reporter: Michael Stack
>Priority: Major
>
> Just want to see that all good if zk wal splitter enabled post HBASE-24632



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24866) Update reporter tool with new release

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24866.
--
Resolution: Done

> Update reporter tool with new release
> -
>
> Key: HBASE-24866
> URL: https://issues.apache.org/jira/browse/HBASE-24866
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24910) Promote RC artifacts in svn

2020-08-19 Thread Nick Dimiduk (Jira)
Nick Dimiduk created HBASE-24910:


 Summary: Promote RC artifacts in svn
 Key: HBASE-24910
 URL: https://issues.apache.org/jira/browse/HBASE-24910
 Project: HBase
  Issue Type: Sub-task
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24910) Promote RC artifacts in svn

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24910.
--
Resolution: Done

> Promote RC artifacts in svn
> ---
>
> Key: HBASE-24910
> URL: https://issues.apache.org/jira/browse/HBASE-24910
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24864) Push signed release tag

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24864.
--
Resolution: Done

> Push signed release tag
> ---
>
> Key: HBASE-24864
> URL: https://issues.apache.org/jira/browse/HBASE-24864
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24863) "Release" staged nexus repository

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24863.
--
Resolution: Done

> "Release" staged nexus repository
> -
>
> Key: HBASE-24863
> URL: https://issues.apache.org/jira/browse/HBASE-24863
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24865) Release version 2.3.1 in Jira

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24865.
--
Resolution: Done

> Release version 2.3.1 in Jira
> -
>
> Key: HBASE-24865
> URL: https://issues.apache.org/jira/browse/HBASE-24865
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24862) Spin RCs

2020-08-19 Thread Nick Dimiduk (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-24862.
--
Resolution: Done

> Spin RCs
> 
>
> Key: HBASE-24862
> URL: https://issues.apache.org/jira/browse/HBASE-24862
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24909) Remove unnecessary ClassNotFoundException and NoSuchMethodException stack traces from HBase startup logs

2020-08-19 Thread Geoffrey Jacoby (Jira)
Geoffrey Jacoby created HBASE-24909:
---

 Summary: Remove unnecessary ClassNotFoundException and 
NoSuchMethodException stack traces from HBase startup logs
 Key: HBASE-24909
 URL: https://issues.apache.org/jira/browse/HBASE-24909
 Project: HBase
  Issue Type: Improvement
Reporter: Geoffrey Jacoby
Assignee: Geoffrey Jacoby


During cluster startup there are a couple of places where HBase needs to use 
reflection to determine what version of Hadoop or protobuf it's using, and then 
instantiate the right class. 

If its first guess is wrong, it logs a ClassNotFoundException (for protobuf 
MessageLite) or NoSuchMethodException (for 
DFSClient.decryptEncryptedDataEncryptionKey). While this is done at DEBUG 
level, the exception types and the stack traces can lead to operators thinking 
something is wrong. 

Since neither the exception nor the stack trace is actually of interest, we 
should just log a brief, clear message at DEBUG level about which decision was 
made and eat the exception without logging it. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (HBASE-24899) [hbase-thirdparty] Add pre commit support for hbase-thirdparty

2020-08-19 Thread Duo Zhang (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-24899.
---
Hadoop Flags: Reviewed
  Resolution: Fixed

Merged to master.

Thanks [~psomogyi] for reviewing.

> [hbase-thirdparty] Add pre commit support for hbase-thirdparty
> --
>
> Key: HBASE-24899
> URL: https://issues.apache.org/jira/browse/HBASE-24899
> Project: HBase
>  Issue Type: Improvement
>  Components: thirdparty
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: thirdparty-3.5.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] The first HBase 2.3.1 release candidate (RC0) is available

2020-08-19 Thread Nick Dimiduk
With 1x +1, 3x +1 (binding), and no other ballots cast, this VOTE passes.
Thank you everyone who spent some time with this release.

On Tue, Aug 18, 2020 at 4:48 PM Nick Dimiduk  wrote:

> +1
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_222): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_222): ok
>  - mvn clean install -DskipTests
> * Built from source (11.0.4): ok
>  - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_222): ok
>  - mvn package -P runSmallTests
> * Unit tests pass (11.0.4): ok
>  - mvn package -P runSmallTests
> * Ran through ITBLL without major incident (HBASE-24896, possibly
> another issue around ServerCrashProcedure, analysis pending)
>
>
> On Tue, Aug 18, 2020 at 9:55 AM Andrew Purtell 
> wrote:
>
>> +1 (binding)
>>
>>  * Signature: ok
>>  * Checksum : ok
>>  * Rat check (1.8.0_265): ok
>>   - mvn clean apache-rat:check
>>  * Built from source (1.8.0_265): ok
>>   - mvn clean install -DskipTests
>>  * Unit tests pass (1.8.0_265): ok*
>>   - mvn package -P runAllTests
>>
>> * - hbase-server unit had a test exceed GC time limits and abort the
>> surefire JVM, but all tests passed with separate invocation.
>>
>>
>> On Wed, Aug 12, 2020 at 1:23 PM Nick Dimiduk  wrote:
>>
>> > Please vote on this Apache hbase release candidate,
>> > hbase-2.3.1RC0
>> >
>> > The VOTE will remain open for at least 72 hours.
>> >
>> > [ ] +1 Release this package as Apache hbase 2.3.1
>> > [ ] -1 Do not release this package because ...
>> >
>> > The tag to be voted on is 2.3.1RC0:
>> >
>> >   https://github.com/apache/hbase/tree/2.3.1RC0
>> >
>> > The release files, including signatures, digests, as well as CHANGES.md
>> > and RELEASENOTES.md included in this RC can be found at:
>> >
>> >   https://dist.apache.org/repos/dist/dev/hbase/2.3.1RC0/
>> >
>> > Maven artifacts are available in a staging repository at:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachehbase-1404/
>> >
>> > Artifacts were signed with the 0x1C3489BD key which can be found in:
>> >
>> >   https://dist.apache.org/repos/dist/release/hbase/KEYS
>> >
>> > To learn more about Apache hbase, please see
>> >
>> >   http://hbase.apache.org/
>> >
>> > Thanks,
>> > Your HBase Release Manager
>> >
>>
>


Re: [VOTE] Third release candidate for hbase-thirdparty 3.4.0 is available for download

2020-08-19 Thread Viraj Jasani
+1

* Signature: ok
* Build from source: ok
* Ran small tests on master branch with #, all good.
* CRUD: ok


On 2020/08/17 08:03:50, 张铎(Duo Zhang)  wrote: 
> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.4.0RC2
> 
> The VOTE will remain open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache hbase thirdparty 3.4.0
> [ ] -1 Do not release this package because ...
> 
> The tag to be voted on is 3.4.0RC2:
> 
>   https://github.com/apache/hbase-thirdparty/tree/3.4.0RC2
> 
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
> 
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-3.4.0RC2/
> 
> Maven artifacts are available in a staging repository at:
> 
>   https://repository.apache.org/content/repositories/orgapachehbase-1405/
> 
> Artifacts were signed with the 9AD2AE49 key which can be found in:
> 
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
> 
> We shade jetty and jersey in this version for addressing the conflicts
> between jetty 9.3 and 9.4, as hadoop recently upgraded its jetty from 9.3
> to 9.4 in patch releases.
> 
> To learn more about Apache hbase thirdparty, please see
> 
>   http://hbase.apache.org/
> 
> Thanks,
> Your HBase Release Manager
> 


[jira] [Created] (HBASE-24908) Correct the description of hbase.offpeak.end.hour

2020-08-19 Thread Zheng Wang (Jira)
Zheng Wang created HBASE-24908:
--

 Summary: Correct the description of hbase.offpeak.end.hour
 Key: HBASE-24908
 URL: https://issues.apache.org/jira/browse/HBASE-24908
 Project: HBase
  Issue Type: Improvement
  Components: documentation
Reporter: Zheng Wang
Assignee: Zheng Wang


The inclusive in description should be exclusive, it will mislead users.

 
{code:java}
@Override
public boolean isOffPeakHour(int targetHour) {
  if (startHour <= endHour) {
return startHour <= targetHour && targetHour < endHour;
  }
  return targetHour < endHour || startHour <= targetHour;
}
{code}
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Third release candidate for hbase-thirdparty 3.4.0 is available for download

2020-08-19 Thread Peter Somogyi
+1 (binding)

signature, checksum: ok
changes, release notes: ok
tarball matches with 3.4.0RC2 tag: ok
build HBase master using # PR: ok

On Mon, Aug 17, 2020 at 10:04 AM 张铎(Duo Zhang) 
wrote:

> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.4.0RC2
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase thirdparty 3.4.0
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 3.4.0RC2:
>
>   https://github.com/apache/hbase-thirdparty/tree/3.4.0RC2
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-3.4.0RC2/
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1405/
>
> Artifacts were signed with the 9AD2AE49 key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> We shade jetty and jersey in this version for addressing the conflicts
> between jetty 9.3 and 9.4, as hadoop recently upgraded its jetty from 9.3
> to 9.4 in patch releases.
>
> To learn more about Apache hbase thirdparty, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>


[jira] [Resolved] (HBASE-24884) BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from command line parameters

2020-08-19 Thread Toshihiro Suzuki (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Toshihiro Suzuki resolved HBASE-24884.
--
Hadoop Flags: Reviewed
  Resolution: Fixed

> BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from 
> command line parameters
> --
>
> Key: HBASE-24884
> URL: https://issues.apache.org/jira/browse/HBASE-24884
> Project: HBase
>  Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.2
>
>
> Currently, BulkLoadHFilesTool/LoadIncrementalHFiles doesn't accept -D options 
> from command line parameters. It should support them.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24907) Turn off the balancer when test region admin api

2020-08-19 Thread Guanghao Zhang (Jira)
Guanghao Zhang created HBASE-24907:
--

 Summary: Turn off the balancer when test region admin api
 Key: HBASE-24907
 URL: https://issues.apache.org/jira/browse/HBASE-24907
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang


For region admin api, we will test move/split/merge/assign/unassign and test 
the region location right or not. But the balancer may move region to other 
places and break the UT. So turn off the balancer for TestAsyncRegionAdminApi.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] The first HBase 2.2.6 release candidate (RC0) is available

2020-08-19 Thread Guanghao Zhang
>
> TestAsyncTableRSCrashPublish


This is an odd one and see HBASE-23850. So I ignore it on branch-2.2.
See  HBASE-24870.

**/master.assignment.TestRaceBetweenSCPAndDTP.java
>

Fixed by HBASE-24819.

**/replication.multiwal.TestReplicationEndpointWithMultipleAsyncWAL.java
> **/replication.multiwal.TestReplicationSyncUpToolWithMultipleWAL.java
>

Not regression. After debug, I thought the reason is that the wait time is
too short. See HBASE-24906.

**/master.procedure.TestHBCKSCP.java

 **/replication.TestReplicationDroppedTables.java

**/replication.TestReplicationSyncUpTool.java

 
org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue

 org.apache.hadoop.hbase.TestSplitMerge.test


These tests were fixed by backport branch-2 UT stabilizing job and not in
flaky dashboard now.

Will prepare the second release candidate of 2.2.6 after resolving the
remaining issues.

 Please start a new, dedicated mail thread with an appropriate [DISCUSS]

subject if you want to move the stable pointer to a new minor release line.


Yeah. I am +1 for moving the stable line to 2.3.*. Will open a [DISCUSS]
thread after 2.2.6 and 2.3.1 are released. Thanks.



Peter Somogyi  于2020年7月23日周四 下午6:46写道:

> +1 (binding)
>
> Signatures & checksums: ok
> Changes, release notes: ok
> Compatibility report: ok
> Rat check: ok
> Built from source: ok
> Unit test: ok
> Shell basic commands: ok
> LTT 1M rows: ok
>
>
> On Mon, Jul 20, 2020 at 5:24 AM Guanghao Zhang  wrote:
>
> > Please vote on this release candidate (RC) for Apache HBase 2.2.6.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 2.2.6
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.2.6RC0. The release files, including
> > signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC0/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachehbase-1401
> >
> > Signatures used for HBase RCs can be found in this file:
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > The list of bug fixes going into 2.2.6 can be found in included
> > CHANGES.md and RELEASENOTES.md available here:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC0/CHANGES.md
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC0/RELEASENOTES.md
> >
> > A detailed source and binary compatibility report for this release is
> > available at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC0/api_compare_2.2.6RC0_to_2.2.5.html
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Guanghao Zhang
> >
>


[jira] [Created] (HBASE-24906) Enalrge the wait time in TestReplicationEndpoint#testInterClusterReplication

2020-08-19 Thread Guanghao Zhang (Jira)
Guanghao Zhang created HBASE-24906:
--

 Summary: Enalrge the wait time in 
TestReplicationEndpoint#testInterClusterReplication
 Key: HBASE-24906
 URL: https://issues.apache.org/jira/browse/HBASE-24906
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang


Failed many times. But the failed reason are different. The replicated entries 
number are different. So it means the replication is work and it need more time 
to replicate all 2500 entries.
h3. Error Message

Waiting timed out after [30,000] msec Failed to replicate all edits, expected = 
2500 replicated = 2499

 
h3. Error Message

Waiting timed out after [30,000] msec Failed to replicate all edits, expected = 
2500 replicated = 2481

 
h3. Error Message

Waiting timed out after [30,000] msec Failed to replicate all edits, expected = 
2500 replicated = 2491



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24905) [hbase-thirdparty] Remove dev_files

2020-08-19 Thread Duo Zhang (Jira)
Duo Zhang created HBASE-24905:
-

 Summary: [hbase-thirdparty] Remove dev_files
 Key: HBASE-24905
 URL: https://issues.apache.org/jira/browse/HBASE-24905
 Project: HBase
  Issue Type: Task
  Components: thirdparty
Reporter: Duo Zhang
Assignee: Duo Zhang
 Fix For: thirdparty-3.5.0


It only contains a make_rc.sh script, but now we use the create-release scripts 
from the main repo, so it is useless now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (HBASE-24904) Split TestAsyncTableAdminApi and TestSnapshotTemporaryDirectoryWithRegionReplicas

2020-08-19 Thread Guanghao Zhang (Jira)
Guanghao Zhang created HBASE-24904:
--

 Summary: Split TestAsyncTableAdminApi and 
TestSnapshotTemporaryDirectoryWithRegionReplicas
 Key: HBASE-24904
 URL: https://issues.apache.org/jira/browse/HBASE-24904
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang


See 
[https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/42/testReport/org.apache.hadoop.hbase.client/TestAsyncTableAdminApi/]

[https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/61/testReport/junit/org.apache.hadoop.hbase.client/TestSnapshotTemporaryDirectoryWithRegionReplicas//]

 

These ut are flaky because they take too much time which more than 780 seconds. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)