[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-4288:
--
Fix Version/s: (was: 0.90.6)
0.90.7
Moving into 0.90.7
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-4288:
--
Fix Version/s: 0.92.0
Already committed to 0.92 and trunk But not into 0.90.
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4288:
-
Resolution: Fixed
Fix Version/s: (was: 0.90.5)
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4288:
-
Fix Version/s: (was: 0.92.0)
0.90.5
Server not running exception during meta
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4288:
-
Attachment: 4288-v2.txt
Test to prove that this no longer an issue. I think we should commit this test
because
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4288:
-
Status: Patch Available (was: Open)
Server not running exception during meta verification causes RS abort
[
https://issues.apache.org/jira/browse/HBASE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4288:
-
Attachment: 4288.txt
I think this scenario unlikely now we have retries in place. Writing a unit
test to prove
