[
https://issues.apache.org/jira/browse/APLO-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925943#comment-13925943
]
Xavi Folch commented on APLO-293:
---------------------------------
Hi Hiram, I have the same problem too! An OOM-killer killed unexpectedly my
Apollo service (it had more heap memory than allowed), so now I can't restore
it.
Is there any patch for this issue? Do I have to delete the data? My version is
1.6
This is my log trace:
{noformat}
2014-03-10 17:47:15,902 | WARN | DB operation failed. (entering recovery
mode): org.iq80.leveldb.DBException: IO error:
/opt/apache-apollo-1.6/bin/myproject/data/dirty.index/058433.sst: No such file
or directory | 144ace41516
2014-03-10 17:47:15,977 | INFO | virtual host startup is waiting on store
startup |
2014-03-10 17:47:17,023 | INFO | DB recovered from failure. |
2014-03-10 17:47:17,024 | ERROR | Store startup failure:
org.iq80.leveldb.DBException: IO error:
/opt/apache-apollo-1.6/bin/myproject/data/dirty.index/058433.sst: No such file
or directory | 144ace41517
2014-03-10 17:47:17,027 | INFO | virtual host startup is no longer waiting.
It waited a total of 2 seconds. |
{noformat}
> 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.8
>
>
> 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.2#6252)
