[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-10809:
---
Fix Version/s: (was: 0.98.2)
0.98.1
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Fix For: 0.98.1, 0.99.0, 0.96.3
Attachments: hbase-10809-v1.patch, hbase-10809.patch,
hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Resolution: Fixed
Fix Version/s: 0.96.3
0.98.2
0.99.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks [~devaraj] [~saint@gmail.com] for the reviews! I've integrated the
patch into 0.96,0.98 trunk branch.
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Fix For: 0.99.0, 0.98.2, 0.96.3
Attachments: hbase-10809-v1.patch, hbase-10809.patch,
hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Status: Patch Available (was: Open)
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.96.1, 0.98.0, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Attachment: hbase-10809.patch
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-10809:
--
Attachment: hbase-10809.patch
Retry. Test failure seems unrelated.
Why this Jeffrey? (We miss you -- Phoenix stole you which is fine for a
while -- but we want you back!)
-for (int tries = 0; tries (this.numRetries *
this.retryLongerMultiplier); tries++) {
+for (int tries = 0; tries this.numRetries; tries++) {
Why remove the retryLongerMultiplier? You don't say.
+1 otherwise.
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809.patch, hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Attachment: hbase-10809-v1.patch
The test failures are due to the test case deletes a table and immediately
recreates it. The connection cache still refer to the deleted table. Not sure
why before doesn't have the issue.
The v1 patch just increases the retry from 1 to 2 in order to update internal
cache.
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809-v1.patch, hbase-10809.patch,
hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Attachment: (was: hbase-10809-v1.patch)
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809.patch, hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10809) HBaseAdmin#deleteTable fails when META region happen to move around same time
[
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-10809:
--
Attachment: hbase-10809-v1.patch
HBaseAdmin#deleteTable fails when META region happen to move around same time
-
Key: HBASE-10809
URL: https://issues.apache.org/jira/browse/HBASE-10809
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.0, 0.96.1, 0.99.0
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Attachments: hbase-10809-v1.patch, hbase-10809.patch,
hbase-10809.patch
The issue is that in the retry loop, we never refetch the latest meta
location. So if meta starts to move right after the function get Meta server
location, the delete table eventually may fail with
{code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1
is not online{code}
Below is the stack trace:
{code}
2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by:
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is
not online
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
2014-01-31 04:02:41,943|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
2014-01-31 04:02:41,944|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
2014-01-31 04:02:41,945|beaver.machine|INFO|
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
2014-01-31 04:02:41,945|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
2014-01-31 04:02:41,946|beaver.machine|INFO|at
org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
