[jira] [Commented] (HBASE-6417) hbck merges .META. regions if there's an old leftover
[ https://issues.apache.org/jira/browse/HBASE-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418769#comment-13418769 ] Jonathan Hsieh commented on HBASE-6417: --- Did you keep a copy of the hbck details before you ran the -repair option? hbck merges .META. regions if there's an old leftover - Key: HBASE-6417 URL: https://issues.apache.org/jira/browse/HBASE-6417 Project: HBase Issue Type: Bug Reporter: Jean-Daniel Cryans Fix For: 0.96.0, 0.94.2 Attachments: hbck.log Trying to see what caused HBASE-6310, one of the things I figured is that the bad .META. row is actually one from the time that we were permitting meta splitting and that folder had just been staying there for a while. So I tried to recreate the issue with -repair and it merged my good .META. region with the one that's 3 years old that also has the same start key. I ended up with a brand new .META. region! I'll be attaching the full log in a separate file. -- 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-6417) hbck merges .META. regions if there's an old leftover
[ https://issues.apache.org/jira/browse/HBASE-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418774#comment-13418774 ] Jean-Daniel Cryans commented on HBASE-6417: --- No, but I can reproduce. hbck merges .META. regions if there's an old leftover - Key: HBASE-6417 URL: https://issues.apache.org/jira/browse/HBASE-6417 Project: HBase Issue Type: Bug Reporter: Jean-Daniel Cryans Fix For: 0.96.0, 0.94.2 Attachments: hbck.log Trying to see what caused HBASE-6310, one of the things I figured is that the bad .META. row is actually one from the time that we were permitting meta splitting and that folder had just been staying there for a while. So I tried to recreate the issue with -repair and it merged my good .META. region with the one that's 3 years old that also has the same start key. I ended up with a brand new .META. region! I'll be attaching the full log in a separate file. -- 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-6417) hbck merges .META. regions if there's an old leftover
[ https://issues.apache.org/jira/browse/HBASE-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418887#comment-13418887 ] Jonathan Hsieh commented on HBASE-6417: --- Feels like we could add an option to not do repairs on META unless forced to. hbck merges .META. regions if there's an old leftover - Key: HBASE-6417 URL: https://issues.apache.org/jira/browse/HBASE-6417 Project: HBase Issue Type: Bug Reporter: Jean-Daniel Cryans Fix For: 0.96.0, 0.94.2 Attachments: hbck.log Trying to see what caused HBASE-6310, one of the things I figured is that the bad .META. row is actually one from the time that we were permitting meta splitting and that folder had just been staying there for a while. So I tried to recreate the issue with -repair and it merged my good .META. region with the one that's 3 years old that also has the same start key. I ended up with a brand new .META. region! I'll be attaching the full log in a separate file. -- 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