You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (Created) (JIRA)" <ji...@apache.org> on 2011/12/13 16:41:31 UTC
[jira] [Created] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Automatic recovery on startup when index is corrupted
-----------------------------------------------------
Key: AMQ-3634
URL: https://issues.apache.org/jira/browse/AMQ-3634
Project: ActiveMQ
Issue Type: New Feature
Affects Versions: 5.5.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.6.0
When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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] [Resolved] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Posted by "Dejan Bosanac (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-3634.
--------------------------------
Resolution: Fixed
Fixed with svn revision 1213743
Additionally, {{archiveCorruptedIndex}} property can be used to specify delete (false) or archive (true) corrupted index - false is a default value.
> Automatic recovery on startup when index is corrupted
> -----------------------------------------------------
>
> Key: AMQ-3634
> URL: https://issues.apache.org/jira/browse/AMQ-3634
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Posted by "Martin Lichtin (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175381#comment-13175381 ]
Martin Lichtin commented on AMQ-3634:
-------------------------------------
Hi Dejan
Are you also handling this case here?
http://activemq.2283324.n4.nabble.com/KahaDB-detecting-corrupt-index-file-td2541943.html
> Automatic recovery on startup when index is corrupted
> -----------------------------------------------------
>
> Key: AMQ-3634
> URL: https://issues.apache.org/jira/browse/AMQ-3634
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Posted by "Dejan Bosanac (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175456#comment-13175456 ]
Dejan Bosanac commented on AMQ-3634:
------------------------------------
Hi Martin,
I don't think so as it seems that the problem isn't caught on startup. If you can create a test that reproduces it, I'd take a look and see if we can deal with that case as well.
> Automatic recovery on startup when index is corrupted
> -----------------------------------------------------
>
> Key: AMQ-3634
> URL: https://issues.apache.org/jira/browse/AMQ-3634
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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] [Resolved] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Posted by "Gary Tully (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3634.
-----------------------------
Resolution: Fixed
index recovery now starts at the beginning of the journal, so there is no message loss. http://svn.apache.org/viewvc?view=rev&rev=1236661
> Automatic recovery on startup when index is corrupted
> -----------------------------------------------------
>
> Key: AMQ-3634
> URL: https://issues.apache.org/jira/browse/AMQ-3634
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Gary Tully
> Fix For: 5.6.0
>
>
> When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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] [Reopened] (AMQ-3634) Automatic recovery on startup when
index is corrupted
Posted by "Gary Tully (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully reopened AMQ-3634:
-----------------------------
Assignee: Gary Tully (was: Dejan Bosanac)
we need to clean up the existing metadata and page file before trying to reload. Depending on the type of corruption, the metadata may load ok, but be invalid. In one example, it updates the journal and recovery does not replay from the start of the journal, so we skip messages.
Am working on fix.
> Automatic recovery on startup when index is corrupted
> -----------------------------------------------------
>
> Key: AMQ-3634
> URL: https://issues.apache.org/jira/browse/AMQ-3634
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Gary Tully
> Fix For: 5.6.0
>
>
> When index is corrupted broker won't start up. Index files need to be deleted and broker restarted. This leads to unnecessary downtime and manual intervention which is prone to error. It'd be better to automatically delete (archive) the index and start recovering in those situations.
--
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