You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@activemq.apache.org by "Frank Wen (JIRA)" <ji...@apache.org> on 2013/12/10 09:47:10 UTC

[jira] [Commented] (APLO-293) Apollo should try to recover messages from a corrupted store

    [ https://issues.apache.org/jira/browse/APLO-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844093#comment-13844093 ] 

Frank Wen commented on APLO-293:
--------------------------------

I have the same problem! Apollo can't restart unless I delete all the data. It's awful. Is there any progress on this issue?

> Apollo should try to recover messages from a corrupted store
> ------------------------------------------------------------
>
>                 Key: APLO-293
>                 URL: https://issues.apache.org/jira/browse/APLO-293
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20130202.135855-180
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.7
>
>
> Due to other bugs (mainly APLO-257 but not only), we sometimes have to kill Apollo the hard way as it would not stop gracefully.
> This almost always leaves the LevelDB store corrupted. When (re)starting, we see messages like:
> 2013-02-03 12:47:13,099 | WARN  | DB operation failed. (entering recovery mode): org.iq80.leveldb.DBException: IO error: /var/lib/apollo/data/dirty.index/001869.sst: No such file or directory | 13c9fe18242
> (see also APLO-282)
> At this point Apollo hangs. The only solution is to kill it once more and completely destroy the message store, loosing all messages :-(
> Could Apollo try to recover at least some messages in these situations instead of hanging during startup?



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)