[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[
https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13140968#comment-13140968
]
ramkrishna.s.vasudevan commented on HBASE-4277:
---
Tests passes...
{code}
testClockSkewDetection(org.apache.hadoop.hbase.master.TestClockSkewDetection):
hostname can't be null
testScanner(org.apache.hadoop.hbase.regionserver.TestScanner): hostname can't
be null
{code}
This failure is not due to the patch for this JIRA.
HRS.closeRegion should be able to close regions with only the encoded name
--
Key: HBASE-4277
URL: https://issues.apache.org/jira/browse/HBASE-4277
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.4
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.90.5
Attachments: HBASE-4277_0.90.patch
As suggested by Stack in HBASE-4217 creating a new issue to provide a patch
for 0.90.x version.
We had some sort of an outage this morning due to a few racks losing power,
and some regions were left in the following state:
ERROR: Region UNKNOWN_REGION on sv4r17s9:60020,
key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on
sv4r17s9:60020
That region was deleted by the master but the region server never got the
memo. Right now there's no way to force close it because HRS.closeRegion
requires an HRI and the only way to create one is to get it from .META. which
in our case doesn't contain a row for that region. Basically we have to wait
until that server is dead to get rid of the region and make hbck happy.
The required change is to have closeRegion accept an encoded name in both HBA
(when the RS address is provided) and HRS since it's able to find it anyways
from it's list of live regions.
bq.If a 0.90 version, we maybe should do that in another issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141289#comment-13141289 ] stack commented on HBASE-4277: -- ++1 on commit (smile) HRS.closeRegion should be able to close regions with only the encoded name -- Key: HBASE-4277 URL: https://issues.apache.org/jira/browse/HBASE-4277 Project: HBase Issue Type: Bug Affects Versions: 0.90.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.90.5 Attachments: HBASE-4277_0.90.patch As suggested by Stack in HBASE-4217 creating a new issue to provide a patch for 0.90.x version. We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. bq.If a 0.90 version, we maybe should do that in another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13140135#comment-13140135 ] ramkrishna.s.vasudevan commented on HBASE-4277: --- The patch applies as is.. If it is ok I can go ahead and commit it. Pls share your comments. HRS.closeRegion should be able to close regions with only the encoded name -- Key: HBASE-4277 URL: https://issues.apache.org/jira/browse/HBASE-4277 Project: HBase Issue Type: Bug Affects Versions: 0.90.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.90.5 Attachments: HBASE-4277_0.90.patch As suggested by Stack in HBASE-4217 creating a new issue to provide a patch for 0.90.x version. We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. bq.If a 0.90 version, we maybe should do that in another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13140270#comment-13140270 ] stack commented on HBASE-4277: -- +1 on commit HRS.closeRegion should be able to close regions with only the encoded name -- Key: HBASE-4277 URL: https://issues.apache.org/jira/browse/HBASE-4277 Project: HBase Issue Type: Bug Affects Versions: 0.90.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.90.5 Attachments: HBASE-4277_0.90.patch As suggested by Stack in HBASE-4217 creating a new issue to provide a patch for 0.90.x version. We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. bq.If a 0.90 version, we maybe should do that in another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13139933#comment-13139933 ] ramkrishna.s.vasudevan commented on HBASE-4277: --- I will see if the patch still applies if not will prepare an updated on and then commit it. Thanks for your review Stack HRS.closeRegion should be able to close regions with only the encoded name -- Key: HBASE-4277 URL: https://issues.apache.org/jira/browse/HBASE-4277 Project: HBase Issue Type: Bug Affects Versions: 0.90.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.90.5 Attachments: HBASE-4277_0.90.patch As suggested by Stack in HBASE-4217 creating a new issue to provide a patch for 0.90.x version. We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. bq.If a 0.90 version, we maybe should do that in another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4277) HRS.closeRegion should be able to close regions with only the encoded name
[ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092846#comment-13092846 ] Ted Yu commented on HBASE-4277: --- +1 on patch. HRS.closeRegion should be able to close regions with only the encoded name -- Key: HBASE-4277 URL: https://issues.apache.org/jira/browse/HBASE-4277 Project: HBase Issue Type: Bug Affects Versions: 0.90.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 0.90.5 Attachments: HBASE-4277_0.90.patch As suggested by Stack in HBASE-4217 creating a new issue to proved a patch for 0.90.x version. We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. bq.If a 0.90 version, we maybe should do that in another issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
