[jira] [Comment Edited] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147347#comment-17147347 ] Yu Wang edited comment on HBASE-24595 at 6/29/20, 1:40 AM: --- Did anyone ever appear this error in this environment and how to solve it ? Thank you very much and sorry if i'm asking silly questions. was (Author: yuwang0...@gmail.com): Did anyone ever appear this error in this environment and how to solve it ? > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster log： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Description: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 hbase shell create namespace blocked when all datanodes has restarted in kerberos environment, but create it successfully without kerberos hmaster log： 2020-06-19 23:47:48,241 WARN [PEWorker-15] procedure.CreateNamespaceProcedure: Retriable error trying to create namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 at org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) at org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) at org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) at org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) at org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) ... 4 more 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 11.264sec 2020-06-19 23:48:04,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 16.264sec 2020-06-19 23:48:09,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 21.265sec 2020-06-19 23:48:14,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 26.265sec 2020-06-19 23:48:19,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 31.265sec 2020-06-19 23:48:24,222 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 36.266sec 2020-06-19 23:48:29,222 WARN
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147347#comment-17147347 ] Yu Wang commented on HBASE-24595: - Did anyone ever appear this error in this environment and how to solve it ? > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec > 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck
[jira] [Comment Edited] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[
https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142683#comment-17142683
]
Yu Wang edited comment on HBASE-24595 at 6/23/20, 7:15 AM:
---
The phenomenon is similar with HBASE-22665 and regionserver log has the same
error log,but not found 'AbstractFSWAL.shutdown' in regionserver jstack.
the regionserver log has error log:
{code:java}
2020-06-23 14:34:11,943 ERROR [MemStoreFlusher.0] regionserver.MemStoreFlusher:
Cache flush failed for region hbase:meta,,1
org.apache.hadoop.hbase.exceptions.TimeoutIOException: Failed to get sync
result after 30 ms for txid=22, WAL system stuck?
at
org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:145)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:586)
at
org.apache.hadoop.hbase.regionserver.HRegion.doSyncOfUnflushedWALChanges(HRegion.java:2674)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2612)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2470)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2444)
at
org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2334)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:612)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:581)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$1000(MemStoreFlusher.java:68)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:361)
at java.lang.Thread.run(Thread.java:748)
2020-06-23 14:34:35,011 WARN
[RpcServer.priority.FPBQ.Fifo.handler=17,queue=1,port=16020] ipc.RpcServer: Can
not complete this request in time, drop it: callId: 28 service: ClientService
methodName: Mutate size: 142 connection: 172.20.100.7:50198 deadline:
1592893834970 param: region=
hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., row=aa1
connection: 172.20.100.7:50198
{code}
was (Author: yuwang0...@gmail.com):
The phenomenon is similar with HBASE-22665 and regionserver log has the same
error log,but not found 'AbstractFSWAL.shutdown' in regionserver jstack.
the regionserver log has error log:
{code:java}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
2020-06-23 14:34:11,943 ERROR [MemStoreFlusher.0] regionserver.MemStoreFlusher:
Cache flush failed for region hbase:meta,,1
org.apache.hadoop.hbase.exceptions.TimeoutIOException: Failed to get sync
result after 30 ms for txid=22, WAL system stuck?
at
org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:145)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:586)
at
org.apache.hadoop.hbase.regionserver.HRegion.doSyncOfUnflushedWALChanges(HRegion.java:2674)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2612)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2470)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2444)
at
org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2334)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:612)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:581)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$1000(MemStoreFlusher.java:68)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:361)
at java.lang.Thread.run(Thread.java:748)
2020-06-23 14:34:35,011 WARN
[RpcServer.priority.FPBQ.Fifo.handler=17,queue=1,port=16020] ipc.RpcServer: Can
not complete this request in time, drop it: callId: 28 service: ClientService
methodName: Mutate size: 142 connection: 172.20.100.7:50198 deadline:
1592893834970 param: region=
hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., row=aa1
connection: 172.20.100.7:50198
> hbase create namespace blocked when all datanodes has restarted
> ---
>
> Key: HBASE-24595
> URL: https://issues.apache.org/jira/browse/HBASE-24595
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.6
>Reporter: Yu Wang
>Priority: Critical
> Attachments:
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142683#comment-17142683 ] Yu Wang commented on HBASE-24595: - The phenomenon is similar with HBASE-22665 and regionserver log has the same error log,but not found 'AbstractFSWAL.shutdown' in regionserver jstack. the regionserver log has error log: 2020-06-23 14:34:11,943 ERROR [MemStoreFlusher.0] regionserver.MemStoreFlusher: Cache flush failed for region hbase:meta,,1 org.apache.hadoop.hbase.exceptions.TimeoutIOException: Failed to get sync result after 30 ms for txid=22, WAL system stuck? at org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:145) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:586) at org.apache.hadoop.hbase.regionserver.HRegion.doSyncOfUnflushedWALChanges(HRegion.java:2674) at org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2612) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2470) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2444) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2334) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:612) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:581) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$1000(MemStoreFlusher.java:68) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:361) at java.lang.Thread.run(Thread.java:748) 2020-06-23 14:34:35,011 WARN [RpcServer.priority.FPBQ.Fifo.handler=17,queue=1,port=16020] ipc.RpcServer: Can not complete this request in time, drop it: callId: 28 service: ClientService methodName: Mutate size: 142 connection: 172.20.100.7:50198 deadline: 1592893834970 param: region= hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., row=aa1 connection: 172.20.100.7:50198 > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at >
[jira] [Comment Edited] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[
https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142683#comment-17142683
]
Yu Wang edited comment on HBASE-24595 at 6/23/20, 7:15 AM:
---
The phenomenon is similar with HBASE-22665 and regionserver log has the same
error log,but not found 'AbstractFSWAL.shutdown' in regionserver jstack.
the regionserver log has error log:
{code:java}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
2020-06-23 14:34:11,943 ERROR [MemStoreFlusher.0] regionserver.MemStoreFlusher:
Cache flush failed for region hbase:meta,,1
org.apache.hadoop.hbase.exceptions.TimeoutIOException: Failed to get sync
result after 30 ms for txid=22, WAL system stuck?
at
org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:145)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:586)
at
org.apache.hadoop.hbase.regionserver.HRegion.doSyncOfUnflushedWALChanges(HRegion.java:2674)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2612)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2470)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2444)
at
org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2334)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:612)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:581)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$1000(MemStoreFlusher.java:68)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:361)
at java.lang.Thread.run(Thread.java:748)
2020-06-23 14:34:35,011 WARN
[RpcServer.priority.FPBQ.Fifo.handler=17,queue=1,port=16020] ipc.RpcServer: Can
not complete this request in time, drop it: callId: 28 service: ClientService
methodName: Mutate size: 142 connection: 172.20.100.7:50198 deadline:
1592893834970 param: region=
hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., row=aa1
connection: 172.20.100.7:50198
was (Author: yuwang0...@gmail.com):
The phenomenon is similar with HBASE-22665 and regionserver log has the same
error log,but not found 'AbstractFSWAL.shutdown' in regionserver jstack.
the regionserver log has error log:
2020-06-23 14:34:11,943 ERROR [MemStoreFlusher.0] regionserver.MemStoreFlusher:
Cache flush failed for region hbase:meta,,1
org.apache.hadoop.hbase.exceptions.TimeoutIOException: Failed to get sync
result after 30 ms for txid=22, WAL system stuck?
at
org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:145)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:586)
at
org.apache.hadoop.hbase.regionserver.HRegion.doSyncOfUnflushedWALChanges(HRegion.java:2674)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2612)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2470)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2444)
at
org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2334)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:612)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:581)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$1000(MemStoreFlusher.java:68)
at
org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:361)
at java.lang.Thread.run(Thread.java:748)
2020-06-23 14:34:35,011 WARN
[RpcServer.priority.FPBQ.Fifo.handler=17,queue=1,port=16020] ipc.RpcServer: Can
not complete this request in time, drop it: callId: 28 service: ClientService
methodName: Mutate size: 142 connection: 172.20.100.7:50198 deadline:
1592893834970 param: region=
hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., row=aa1
connection: 172.20.100.7:50198
> hbase create namespace blocked when all datanodes has restarted
> ---
>
> Key: HBASE-24595
> URL: https://issues.apache.org/jira/browse/HBASE-24595
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.6
>Reporter: Yu Wang
>Priority: Critical
> Attachments: create_namespace_1.png,
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142563#comment-17142563 ] Yu Wang commented on HBASE-24595: - Thanks for your answer [~anoop.hbase] I think this scenes is different from HBASE-21564, Seems this is relate to kerberos for working fine in without kerberos environment, but i can't find any kerberos info in master and regionserver log. Doubt that regionserver is interact with kerberos where has problem. > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141957#comment-17141957 ] Yu Wang commented on HBASE-24595: - [~anoop.hbase] put value on table and create table are all blocked > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec > 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171),
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141939#comment-17141939 ] Yu Wang commented on HBASE-24595: - [~zhangduo] could you paste jira number so that I can research it > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec > 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171),
[jira] [Comment Edited] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141939#comment-17141939 ] Yu Wang edited comment on HBASE-24595 at 6/22/20, 11:32 AM: [~zhangduo] could you paste jira number so that I can research it thanks was (Author: yuwang0...@gmail.com): [~zhangduo] could you paste jira number so that I can research it > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck
[jira] [Commented] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141838#comment-17141838 ] Yu Wang commented on HBASE-24595: - modify hbase.wal.provider= filesystem can resolve it > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > > hmaster日志中显示： > 2020-06-19 23:47:48,241 WARN [PEWorker-15] > procedure.CreateNamespaceProcedure: Retriable error trying to create > namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) > java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: > Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at > region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., > hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 > at > org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) > at > org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) > at > org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to > hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: > org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) > at > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) > at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) > at > org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, > waitTime=10763, rpcTimeout=10759 > at > org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) > ... 4 more > 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec > 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec > 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: > Worker stuck PEWorker-15(pid=171), run time
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Description: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 hbase shell create namespace blocked when all datanodes has restarted in kerberos environment, but create it successfully without kerberos hmaster日志中显示： 2020-06-19 23:47:48,241 WARN [PEWorker-15] procedure.CreateNamespaceProcedure: Retriable error trying to create namespace=abcd2 (in state=CREATE_NAMESPACE_INSERT_INTO_NS_TABLE) java.net.SocketTimeoutException: callTimeout=120, callDuration=1220061: Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 row 'abcd2' on table 'hbase:namespace' at region=hbase:namespace,,1592548148073.f5c7e71fb5e5cab3b27e52600996f7fd., hostname=hadoop-hbnn0005.com,16020,1592580274989, seqNum=162 at org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:159) at org.apache.hadoop.hbase.client.HTable.put(HTable.java:542) at org.apache.hadoop.hbase.master.TableNamespaceManager.insertIntoNSTable(TableNamespaceManager.java:167) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.insertIntoNSTable(CreateNamespaceProcedure.java:240) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:85) at org.apache.hadoop.hbase.master.procedure.CreateNamespaceProcedure.executeFromState(CreateNamespaceProcedure.java:39) at org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:189) at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:965) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1723) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1462) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1200(ProcedureExecutor.java:78) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:2039) Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call to hadoop-hbnn0005.com/172.20.101.36:16020 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:205) at org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390) at org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95) at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410) at org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406) at org.apache.hadoop.hbase.ipc.Call.setTimeout(Call.java:96) at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:199) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:682) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:757) at org.apache.hbase.thirdparty.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:485) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=116, waitTime=10763, rpcTimeout=10759 at org.apache.hadoop.hbase.ipc.RpcConnection$1.run(RpcConnection.java:200) ... 4 more 2020-06-19 23:47:49,218 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 1.262sec 2020-06-19 23:47:54,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 6.263sec 2020-06-19 23:47:59,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 11.264sec 2020-06-19 23:48:04,220 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 16.264sec 2020-06-19 23:48:09,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 21.265sec 2020-06-19 23:48:14,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 26.265sec 2020-06-19 23:48:19,221 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 31.265sec 2020-06-19 23:48:24,222 WARN [ProcExecTimeout] procedure2.ProcedureExecutor: Worker stuck PEWorker-15(pid=171), run time 20mins, 36.266sec 2020-06-19 23:48:29,222 WARN
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: hmaster.log > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: hregionserver.log > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.log, hmaster.png, hmaster_4569.jstack, hregionserver.log, > hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: hmaster_4569.jstack > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.png, hmaster_4569.jstack, hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: hregionserver_25649.jstack > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.png, hmaster_4569.jstack, hregionserver_25649.jstack, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: create_namespace_2.png create_namespace_1.png > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: create_namespace_1.png, create_namespace_2.png, > hmaster.png, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: procedure.png > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: hmaster.png, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Attachment: hmaster.png > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > Attachments: hmaster.png, procedure.png > > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Description: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 hbase shell create namespace blocked when all datanodes has restarted in kerberos environment, but create it successfully without kerberos was: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 hbase shell create namespace blocked when all datanodes has restarted in kerberos environment but create it successfully without kerberos > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment, > but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Description: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 hbase shell create namespace blocked when all datanodes has restarted in kerberos environment but create it successfully without kerberos was: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > hbase shell create namespace blocked when all datanodes has restarted > in kerberos environment but create it successfully without kerberos > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Description: environment: jdk:1.8.0_181 hadoop: 3.1.1 hbase: 2.1.6 > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > > environment: > jdk:1.8.0_181 > hadoop: 3.1.1 > hbase: 2.1.6 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Component/s: (was: hbase-thirdparty) > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
[ https://issues.apache.org/jira/browse/HBASE-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24595: Component/s: hbase-thirdparty > hbase create namespace blocked when all datanodes has restarted > --- > > Key: HBASE-24595 > URL: https://issues.apache.org/jira/browse/HBASE-24595 > Project: HBase > Issue Type: Bug > Components: hbase-thirdparty >Affects Versions: 2.1.6 >Reporter: Yu Wang >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24595) hbase create namespace blocked when all datanodes has restarted
Yu Wang created HBASE-24595: --- Summary: hbase create namespace blocked when all datanodes has restarted Key: HBASE-24595 URL: https://issues.apache.org/jira/browse/HBASE-24595 Project: HBase Issue Type: Bug Affects Versions: 2.1.6 Reporter: Yu Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24137) The max merge count of metafixer may be remind in hbase-site.xml
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24137: Summary: The max merge count of metafixer may be remind in hbase-site.xml (was: The max merge count of metafixer should be configurable in MetaFixer) > The max merge count of metafixer may be remind in hbase-site.xml > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081104#comment-17081104 ] Yu Wang commented on HBASE-24137: - [~ndimiduk]sorry, I don't understand about "but it's still a configuration parameter of HBase". could you kindly help to advise? what I mean if I want to change the value of hbase.master.metafixer.max.merge.count to 11, i wouldn't have anywhere to change it. > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080177#comment-17080177 ] Yu Wang commented on HBASE-24137: - [~ndimiduk] Thanks for your suggestion. I have opened the githup PR, but i don't find the configuration hbase.master.metafixer.max.merge.count that has exposed to configuration. > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078856#comment-17078856 ] Yu Wang commented on HBASE-24137: - [~ndimiduk] Please review it , Thanks > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078852#comment-17078852 ] Yu Wang commented on HBASE-24137: - [~yuzhih...@gmail.com] Please review it , Thanks > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24137: Fix Version/s: 3.0.0 > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24137: Affects Version/s: (was: thirdparty-3.0.0) 3.0.0 > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24137: Affects Version/s: thirdparty-3.0.0 Status: Patch Available (was: Open) > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Affects Versions: thirdparty-3.0.0 >Reporter: Yu Wang >Priority: Minor > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
[ https://issues.apache.org/jira/browse/HBASE-24137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-24137: Attachment: 24137_master_1.patch > The max merge count of metafixer should be configurable in MetaFixer > > > Key: HBASE-24137 > URL: https://issues.apache.org/jira/browse/HBASE-24137 > Project: HBase > Issue Type: Improvement >Reporter: Yu Wang >Priority: Minor > Attachments: 24137_master_1.patch > > > The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24137) The max merge count of metafixer should be configurable in MetaFixer
Yu Wang created HBASE-24137: --- Summary: The max merge count of metafixer should be configurable in MetaFixer Key: HBASE-24137 URL: https://issues.apache.org/jira/browse/HBASE-24137 Project: HBase Issue Type: Improvement Reporter: Yu Wang The max merge count of metafixer should be configurable in MetaFixer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-20449) The minimun number of regions should be configurable in Normalizer
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443437#comment-16443437 ] Yu Wang edited comment on HBASE-20449 at 4/19/18 1:27 AM: -- [~yuzhih...@gmail.com] [~Apache9].Thanks for your comments was (Author: gentlewang): [~yuzhih...@gmail.com] Thanks for your comments > The minimun number of regions should be configurable in Normalizer > -- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 20449_master_1.patch, HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) The minimun number of regions should be configurable in Normalizer
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443437#comment-16443437 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] Thanks for your comments > The minimun number of regions should be configurable in Normalizer > -- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: 20449_master_1.patch, HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442509#comment-16442509 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] I don't have a backup, the newest patch doesn't have checkstyle warnings. Thanks > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442433#comment-16442433 ] Yu Wang edited comment on HBASE-20449 at 4/18/18 12:39 PM: --- [~yuzhih...@gmail.com] , [~Apache9] thanks HBASE-20449_005.patch I have deleted it,HBASE-20449_master_1.patch is the newest file. was (Author: gentlewang): [~yuzhih...@gmail.com] , [~Apache9] thanks HBASE-20449_005.patch I have delete it,HBASE-20449_master_1.patch is the newest file. > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442433#comment-16442433 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] , [~Apache9] thanks HBASE-20449_005.patch I have delete it,HBASE-20449_master_1.patch is the newest file. > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442356#comment-16442356 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] I have put the org.apache.hadoop.hbase.HBaseConfiguration ahead of org.apache.hadoop.hbase.HBaseIOException, why Wrong order? Thanks > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Comment: was deleted (was: [~yuzhih...@gmail.com] can not submit to master branch?) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_009.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_007.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_004.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_008.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_003.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_006.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_002.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_005.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_007.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_001.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_002.patch, HBASE-20449_003.patch, > HBASE-20449_004.patch, HBASE-20449_005.patch, HBASE-20449_006.patch, > HBASE-20449_007.patch, HBASE-20449_008.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_master_1.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_002.patch, HBASE-20449_003.patch, > HBASE-20449_004.patch, HBASE-20449_005.patch, HBASE-20449_006.patch, > HBASE-20449_007.patch, HBASE-20449_008.patch, HBASE-20449_009.patch, > HBASE-20449_master_1.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1644#comment-1644 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] can not submit to master branch? > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch, HBASE-20449_008.patch, > HBASE-20449_009.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_009.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch, HBASE-20449_008.patch, > HBASE-20449_009.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_009.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch, HBASE-20449_008.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_009.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch, HBASE-20449_008.patch, > HBASE-20449_009.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_008.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch, HBASE-20449_008.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_007.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_007.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_007.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch, HBASE-20449_007.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_006.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch, > HBASE-20449_006.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442090#comment-16442090 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] I have edited it Thanks > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_005.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch, HBASE-20449_005.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442074#comment-16442074 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] I have resubmitted HBASE-20449_004.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_004.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch, HBASE-20449_004.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441895#comment-16441895 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] thank you for your answer ! I have already edited it. > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_003.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441874#comment-16441874 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com] thank you for your answer ! I have already edited it. > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: (was: HBASE-20449_003.patch) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Comment: was deleted (was: [~yuzhih...@gmail.com] thank you for your answer ! I have already edited it.) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_003.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch, > HBASE-20449_003.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441807#comment-16441807 ] Yu Wang commented on HBASE-20449: - [~yuzhih...@gmail.com]Thank you for reviewing. > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_002.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch, HBASE-20449_002.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441787#comment-16441787 ] Yu Wang commented on HBASE-20421: - In addition to indentation,there is no difference between patch v1 and v2. I don't quit understand that extracting the enclosed code into its own method ! Thanks > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch, HBASE-20421_master_2.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Attachment: HBASE-20449_001.patch > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20449: Status: Patch Available (was: Open) > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-20449) the minimun number of region should be configurable in normalizable
[ https://issues.apache.org/jira/browse/HBASE-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang reassigned HBASE-20449: --- Assignee: Yu Wang > the minimun number of region should be configurable in normalizable > --- > > Key: HBASE-20449 > URL: https://issues.apache.org/jira/browse/HBASE-20449 > Project: HBase > Issue Type: Improvement > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Assignee: Yu Wang >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-20449_001.patch > > > the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20449) the minimun number of region should be configurable in normalizable
Yu Wang created HBASE-20449: --- Summary: the minimun number of region should be configurable in normalizable Key: HBASE-20449 URL: https://issues.apache.org/jira/browse/HBASE-20449 Project: HBase Issue Type: Improvement Components: hbase Affects Versions: 3.0.0 Reporter: Yu Wang Fix For: 3.0.0 the minimun number of region should be configurable in normalizable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: HBASE-20421_master_2.patch > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch, HBASE-20421_master_2.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: (was: HBASE-20421_master_2.patch) > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch, HBASE-20421_master_2.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440309#comment-16440309 ] Yu Wang commented on HBASE-20421: - [~yuzhih...@gmail.com] thank you for your answer, I resubmitted a HBASE-20421_master_2.patch file. if there is a error in (try catch), connection will not close. > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch, HBASE-20421_master_2.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: HBASE-20421_master_2.patch > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch, HBASE-20421_master_2.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Affects Version/s: (was: 3.0.0) > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Fix Version/s: (was: 1.2.6) 3.0.0 > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 3.0.0 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Affects Version/s: (was: 1.2.6) 3.0.0 > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 3.0.0 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: HBASE-20421_master_1.patch > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch, > HBASE-20421_master_1.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: HBASE-20421_master.patch > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch, HBASE-20421_master.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Status: Patch Available (was: Open) > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Status: Open (was: Patch Available) > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Status: Patch Available (was: Open) > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20421) HBasecontext creates a connection but does not turn it off
[ https://issues.apache.org/jira/browse/HBASE-20421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Wang updated HBASE-20421: Attachment: HBASE-20421.patch > HBasecontext creates a connection but does not turn it off > -- > > Key: HBASE-20421 > URL: https://issues.apache.org/jira/browse/HBASE-20421 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6 >Reporter: Yu Wang >Priority: Major > Labels: patch > Fix For: 1.2.6 > > Attachments: HBASE-20421.patch > > > HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20421) HBasecontext creates a connection but does not turn it off
Yu Wang created HBASE-20421: --- Summary: HBasecontext creates a connection but does not turn it off Key: HBASE-20421 URL: https://issues.apache.org/jira/browse/HBASE-20421 Project: HBase Issue Type: Bug Components: hbase Affects Versions: 1.2.6 Reporter: Yu Wang Fix For: 1.2.6 HBasecontext creates a connection but does not turn it off -- This message was sent by Atlassian JIRA (v7.6.3#76005)
