[jira] [Updated] (HBASE-21199) Race in region opening and load balancing can cause region stuck in RIT
[ https://issues.apache.org/jira/browse/HBASE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21199: -- Resolution: Duplicate Status: Resolved (was: Patch Available) Will be resolved by HBASE-21217. > Race in region opening and load balancing can cause region stuck in RIT > --- > > Key: HBASE-21199 > URL: https://issues.apache.org/jira/browse/HBASE-21199 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-21199-v1.patch, HBASE-21199.patch > > > After HBASE-20881, when region server calls reportRegionTransition with OPEN > state, we will update the hbase:meta directly and finish the TRSP. So it is > possible that we schedule a new TRSP immediately for this region. But at RS > side, the region opening may still in progress, think of the rpc connection > between master and RS is broken and RS haven't gotten the return value and > still trying to call reportRegionTransition again... So at RS side, it is > possible that the RS finds out that the region we want to close is still > opening and causes problems. > I have set up a cluster to test the synchronous replication and the balancer > for one of the clusters is a bit strange, as it keeps moving the > hbase:namespace region and finally hit the problem described above. > We hit this error first > {noformat} > 2018-09-16,11:42:11,218 WARN [RSProcedureDispatcher-pool3-t4004] > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher: Failed > dispatch to server=c4-hadoop-tst-st57.bj,17200,1536907673199 try=0 > org.apache.hadoop.hbase.NotServingRegionException: > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) > at sun.reflect.GeneratedConstructorAccessor30.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:100) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:90) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:365) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:342) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:349) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:313) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException): > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at >
[jira] [Updated] (HBASE-21199) Race in region opening and load balancing can cause region stuck in RIT
[ https://issues.apache.org/jira/browse/HBASE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21199: -- Attachment: HBASE-21199-v1.patch > Race in region opening and load balancing can cause region stuck in RIT > --- > > Key: HBASE-21199 > URL: https://issues.apache.org/jira/browse/HBASE-21199 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-21199-v1.patch, HBASE-21199.patch > > > After HBASE-20881, when region server calls reportRegionTransition with OPEN > state, we will update the hbase:meta directly and finish the TRSP. So it is > possible that we schedule a new TRSP immediately for this region. But at RS > side, the region opening may still in progress, think of the rpc connection > between master and RS is broken and RS haven't gotten the return value and > still trying to call reportRegionTransition again... So at RS side, it is > possible that the RS finds out that the region we want to close is still > opening and causes problems. > I have set up a cluster to test the synchronous replication and the balancer > for one of the clusters is a bit strange, as it keeps moving the > hbase:namespace region and finally hit the problem described above. > We hit this error first > {noformat} > 2018-09-16,11:42:11,218 WARN [RSProcedureDispatcher-pool3-t4004] > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher: Failed > dispatch to server=c4-hadoop-tst-st57.bj,17200,1536907673199 try=0 > org.apache.hadoop.hbase.NotServingRegionException: > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) > at sun.reflect.GeneratedConstructorAccessor30.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:100) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:90) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:365) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:342) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:349) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:313) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException): > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at >
[jira] [Updated] (HBASE-21199) Race in region opening and load balancing can cause region stuck in RIT
[ https://issues.apache.org/jira/browse/HBASE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21199: -- Attachment: HBASE-21199.patch > Race in region opening and load balancing can cause region stuck in RIT > --- > > Key: HBASE-21199 > URL: https://issues.apache.org/jira/browse/HBASE-21199 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Duo Zhang >Priority: Critical > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-21199.patch > > > After HBASE-20881, when region server calls reportRegionTransition with OPEN > state, we will update the hbase:meta directly and finish the TRSP. So it is > possible that we schedule a new TRSP immediately for this region. But at RS > side, the region opening may still in progress, think of the rpc connection > between master and RS is broken and RS haven't gotten the return value and > still trying to call reportRegionTransition again... So at RS side, it is > possible that the RS finds out that the region we want to close is still > opening and causes problems. > I have set up a cluster to test the synchronous replication and the balancer > for one of the clusters is a bit strange, as it keeps moving the > hbase:namespace region and finally hit the problem described above. > We hit this error first > {noformat} > 2018-09-16,11:42:11,218 WARN [RSProcedureDispatcher-pool3-t4004] > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher: Failed > dispatch to server=c4-hadoop-tst-st57.bj,17200,1536907673199 try=0 > org.apache.hadoop.hbase.NotServingRegionException: > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) > at sun.reflect.GeneratedConstructorAccessor30.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:100) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:90) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:365) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:342) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:349) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:313) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException): > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at >
[jira] [Updated] (HBASE-21199) Race in region opening and load balancing can cause region stuck in RIT
[ https://issues.apache.org/jira/browse/HBASE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21199: -- Assignee: Duo Zhang Status: Patch Available (was: Open) > Race in region opening and load balancing can cause region stuck in RIT > --- > > Key: HBASE-21199 > URL: https://issues.apache.org/jira/browse/HBASE-21199 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-21199.patch > > > After HBASE-20881, when region server calls reportRegionTransition with OPEN > state, we will update the hbase:meta directly and finish the TRSP. So it is > possible that we schedule a new TRSP immediately for this region. But at RS > side, the region opening may still in progress, think of the rpc connection > between master and RS is broken and RS haven't gotten the return value and > still trying to call reportRegionTransition again... So at RS side, it is > possible that the RS finds out that the region we want to close is still > opening and causes problems. > I have set up a cluster to test the synchronous replication and the balancer > for one of the clusters is a bit strange, as it keeps moving the > hbase:namespace region and finally hit the problem described above. > We hit this error first > {noformat} > 2018-09-16,11:42:11,218 WARN [RSProcedureDispatcher-pool3-t4004] > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher: Failed > dispatch to server=c4-hadoop-tst-st57.bj,17200,1536907673199 try=0 > org.apache.hadoop.hbase.NotServingRegionException: > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) > at sun.reflect.GeneratedConstructorAccessor30.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:100) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:90) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:365) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:342) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:349) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:313) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException): > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at >
[jira] [Updated] (HBASE-21199) Race in region opening and load balancing can cause region stuck in RIT
[ https://issues.apache.org/jira/browse/HBASE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21199: -- Priority: Critical (was: Major) > Race in region opening and load balancing can cause region stuck in RIT > --- > > Key: HBASE-21199 > URL: https://issues.apache.org/jira/browse/HBASE-21199 > Project: HBase > Issue Type: Sub-task > Components: amv2 >Reporter: Duo Zhang >Priority: Critical > Fix For: 3.0.0, 2.2.0 > > > After HBASE-20881, when region server calls reportRegionTransition with OPEN > state, we will update the hbase:meta directly and finish the TRSP. So it is > possible that we schedule a new TRSP immediately for this region. But at RS > side, the region opening may still in progress, think of the rpc connection > between master and RS is broken and RS haven't gotten the return value and > still trying to call reportRegionTransition again... So at RS side, it is > possible that the RS finds out that the region we want to close is still > opening and causes problems. > I have set up a cluster to test the synchronous replication and the balancer > for one of the clusters is a bit strange, as it keeps moving the > hbase:namespace region and finally hit the problem described above. > We hit this error first > {noformat} > 2018-09-16,11:42:11,218 WARN [RSProcedureDispatcher-pool3-t4004] > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher: Failed > dispatch to server=c4-hadoop-tst-st57.bj,17200,1536907673199 try=0 > org.apache.hadoop.hbase.NotServingRegionException: > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) > at sun.reflect.GeneratedConstructorAccessor30.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:100) > at > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:90) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:365) > at > org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:342) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.sendRequest(RSProcedureDispatcher.java:349) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:313) > at > org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$ExecuteProceduresRemoteCall.call(RSProcedureDispatcher.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException): > org.apache.hadoop.hbase.NotServingRegionException: The region > 7035a1c2da68172f6f9cec99e00b0ce1 was opening but not yet served. Opening is > cancelled. > at > org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:3167) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.closeRegion(RSRpcServices.java:1635) > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.executeProcedures(RSRpcServices.java:3680) > at > org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28704) > at