activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] [Commented] (APLO-293) Apollo should try to recover messages from a corrupted store
Date Tue, 05 Feb 2013 16:03:12 GMT


Hiram Chirino commented on APLO-293:

Ok.  For some reason, doing an index repair on those data files does not actually get them
working again.  I'm going to have to report a bug against the leveldb c++ impl to see if they
can figure out why the repair did not work.  

On the bright side, if the index repair does not work, we now transition the virtual host
to the STOPPED state.
> Apollo should try to recover messages from a corrupted store
> ------------------------------------------------------------
>                 Key: APLO-293
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20130202.135855-180
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.6
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message