[jira] [Reopened] (HBASE-26993) Make the new framework for region replication could work for SKIP_WAL

2022-06-03 Thread chenglei (Jira)


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

chenglei reopened HBASE-26993:
--

> Make the new framework for region replication could work for SKIP_WAL
> -
>
> Key: HBASE-26993
> URL: https://issues.apache.org/jira/browse/HBASE-26993
> Project: HBase
>  Issue Type: Improvement
>  Components: read replicas
>Affects Versions: 3.0.0-alpha-2
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 3.0.0-alpha-3
>
>
> For now , the new region replication framework introduced by HBASE-26233 
> could not work for table which {{DURABILITY}} is {{Durability.SKIP_WAL}}, but 
> the framework does not build on WAL replication, so it should also work for 
> SKIP_WAL, and besides  table could be SKIP_WAL, the individual {{Mutation}}  
> could also be SKIP_WAL. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Resolved] (HBASE-26649) Support meta replica LoadBalance mode for RegionLocator#getAllRegionLocations()

2022-06-03 Thread Huaxiang Sun (Jira)


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

Huaxiang Sun resolved HBASE-26649.
--
Fix Version/s: 2.5.0
   3.0.0-alpha-3
   2.4.13
 Release Note: When setting 'hbase.locator.meta.replicas.mode' to 
"LoadBalance" at HBase client, RegionLocator#getAllRegionLocations() now load 
balances across all Meta Replica Regions. Please note,  results from 
non-primary meta replica regions may contain stale data. 
   Resolution: Fixed

> Support meta replica LoadBalance mode for 
> RegionLocator#getAllRegionLocations()
> ---
>
> Key: HBASE-26649
> URL: https://issues.apache.org/jira/browse/HBASE-26649
> Project: HBase
>  Issue Type: Improvement
>  Components: meta replicas
>Affects Versions: 2.4.9
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.13
>
>
> When HBase application restarts, its meta cache is empty. Normally, it will 
> fill the meta cache one region at a time by scanning the meta region. This 
> will cause huge pressure to the region server hosting meta during application 
> restart. 
> It can prefetching all region locations by calling 
> RegionLocator#getAllRegionLocations().Meta replica LoadBalance mode is 
> support in 2.4, it will be nice to load balance 
> RegionLocator#getAllRegionLocations() to all meta replica regions so batch 
> scan can spread across all meta replica regions.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (HBASE-27087) TestQuotaThrottle times out in branch-2.5.

2022-06-03 Thread Huaxiang Sun (Jira)
Huaxiang Sun created HBASE-27087:


 Summary: TestQuotaThrottle times out in branch-2.5.
 Key: HBASE-27087
 URL: https://issues.apache.org/jira/browse/HBASE-27087
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 2.5.0
Reporter: Huaxiang Sun


With branch-2.5, TestQuotaThrottle times out. Need to investigate.

 
h3. Error Message

Failed after attempts=7, exceptions: 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master 2022-06-03T11:26:33.418Z, 
RpcRetryingCaller\{globalStartTime=2022-06-03T11:26:33.418Z, pause=250, 
maxAttempts=7}, org.apache.hadoop.hbase.MasterNotRunningException: 
java.io.IOException: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for /hbase/master



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Resolved] (HBASE-27004) Client integration test is failing on branch-2.x

2022-06-03 Thread Duo Zhang (Jira)


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

Duo Zhang resolved HBASE-27004.
---
Resolution: Fixed

Fixed by INFRA.

> Client integration test is failing on branch-2.x
> 
>
> Key: HBASE-27004
> URL: https://issues.apache.org/jira/browse/HBASE-27004
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Priority: Major
>
> It is because we can not start hadoop cluster.
> The error is
> {noformat}
> 22/05/05 20:04:18 INFO service.AbstractService: Service HistoryClientService 
> failed in state STARTED; cause: 
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: 
> java.net.BindException: Problem binding to [jenkins-hbase3.apache.org:0] 
> java.net.BindException: Cannot assign requested address; For more details 
> see:  http://wiki.apache.org/hadoop/BindException
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: 
> java.net.BindException: Problem binding to [jenkins-hbase3.apache.org:0] 
> java.net.BindException: Cannot assign requested address; For more details 
> see:  http://wiki.apache.org/hadoop/BindException
>   at 
> org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.getServer(RpcServerFactoryPBImpl.java:138)
>   at 
> org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC.getServer(HadoopYarnProtoRPC.java:65)
>   at org.apache.hadoop.yarn.ipc.YarnRPC.getServer(YarnRPC.java:54)
>   at 
> org.apache.hadoop.mapreduce.v2.hs.HistoryClientService.serviceStart(HistoryClientService.java:128)
>   at 
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
>   at 
> org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:121)
>   at 
> org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.serviceStart(JobHistoryServer.java:202)
>   at 
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
>   at 
> org.apache.hadoop.mapreduce.v2.MiniMRYarnCluster$JobHistoryServerWrapper$1.run(MiniMRYarnCluster.java:236)
> Caused by: java.net.BindException: Problem binding to 
> [jenkins-hbase3.apache.org:0] java.net.BindException: Cannot assign requested 
> address; For more details see:  http://wiki.apache.org/hadoop/BindException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:824)
>   at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:735)
>   at org.apache.hadoop.ipc.Server.bind(Server.java:615)
>   at org.apache.hadoop.ipc.Server$Listener.(Server.java:1179)
>   at org.apache.hadoop.ipc.Server.(Server.java:2983)
>   at org.apache.hadoop.ipc.RPC$Server.(RPC.java:1003)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server.(ProtobufRpcEngine.java:425)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:346)
>   at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:844)
>   at 
> org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.createServer(RpcServerFactoryPBImpl.java:168)
>   at 
> org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.getServer(RpcServerFactoryPBImpl.java:131)
>   ... 8 more
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:438)
>   at sun.nio.ch.Net.bind(Net.java:430)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at org.apache.hadoop.ipc.Server.bind(Server.java:598)
>   ... 16 more
> {noformat}
> https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/534/artifact/output-integration/hadoop-2/hadoop_cluster_command.err/*view*/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (HBASE-27086) graceful_stop cannot take previous balancer status by incompatibility of hbase shell prompt

2022-06-03 Thread Shinya Yoshida (Jira)
Shinya Yoshida created HBASE-27086:
--

 Summary: graceful_stop cannot take previous balancer status by 
incompatibility of hbase shell prompt
 Key: HBASE-27086
 URL: https://issues.apache.org/jira/browse/HBASE-27086
 Project: HBase
  Issue Type: Bug
Reporter: Shinya Yoshida






--
This message was sent by Atlassian Jira
(v8.20.7#820007)