[jira] [Updated] (HBASE-10955) HBCK leaves the region in masters in-memory RegionStates if region hdfs dir is lost
[
https://issues.apache.org/jira/browse/HBASE-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-10955:
--
Resolution: Fixed
Fix Version/s: (was: 0.98.2)
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Devaraj for review. I've committed this to trunk.
Andrew, Stack do you guys want it?
HBCK leaves the region in masters in-memory RegionStates if region hdfs dir
is lost
---
Key: HBASE-10955
URL: https://issues.apache.org/jira/browse/HBASE-10955
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 0.99.0
Attachments: hbase-10955.v1.patch
One of our tests removes the hdfs directory for the region, and invokes HBCK
to fix the issue. This test fails flakily because the region is removed from
meta and unassigned, but the region is not offlined from the masters
in-memory. This affects further LB runs and disable table, etc.
In case of {{inMeta !inHdfs isDeployed}}, we should not just close the
region from RS, but call master.unassign().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10955) HBCK leaves the region in masters in-memory RegionStates if region hdfs dir is lost
[
https://issues.apache.org/jira/browse/HBASE-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-10955:
--
Attachment: hbase-10955.v1.patch
This fixes the condition defined above. Also we no longer create the HLog
unnecessarily.
HBCK leaves the region in masters in-memory RegionStates if region hdfs dir
is lost
---
Key: HBASE-10955
URL: https://issues.apache.org/jira/browse/HBASE-10955
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 0.99.0, 0.98.2
Attachments: hbase-10955.v1.patch
One of our tests removes the hdfs directory for the region, and invokes HBCK
to fix the issue. This test fails flakily because the region is removed from
meta and unassigned, but the region is not offlined from the masters
in-memory. This affects further LB runs and disable table, etc.
In case of {{inMeta !inHdfs isDeployed}}, we should not just close the
region from RS, but call master.unassign().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10955) HBCK leaves the region in masters in-memory RegionStates if region hdfs dir is lost
[
https://issues.apache.org/jira/browse/HBASE-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-10955:
---
Status: Patch Available (was: Open)
HBCK leaves the region in masters in-memory RegionStates if region hdfs dir
is lost
---
Key: HBASE-10955
URL: https://issues.apache.org/jira/browse/HBASE-10955
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 0.99.0, 0.98.2
Attachments: hbase-10955.v1.patch
One of our tests removes the hdfs directory for the region, and invokes HBCK
to fix the issue. This test fails flakily because the region is removed from
meta and unassigned, but the region is not offlined from the masters
in-memory. This affects further LB runs and disable table, etc.
In case of {{inMeta !inHdfs isDeployed}}, we should not just close the
region from RS, but call master.unassign().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
