You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/02/06 14:26:42 UTC
[jira] [Closed] (AMQ-5556) Log that we are doing recovery when in
LevelDB
[ https://issues.apache.org/jira/browse/AMQ-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon closed AMQ-5556.
---------------------------------------
Resolution: Won't Fix
LevelDB has been deprecated and is no longer supported.
> Log that we are doing recovery when in LevelDB
> ----------------------------------------------
>
> Key: AMQ-5556
> URL: https://issues.apache.org/jira/browse/AMQ-5556
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
> Affects Versions: 5.10.0
> Reporter: Kevin Burton
>
> If ActiveMQ is improperly shut down, LevelDB will have to perform recover.
> However, this can take a LONG time and right now is bottlenecked on a single core. This means it's not immediately apparent what ActiveMQ is doing during this time.
> Printing a message like:
> "ActiveMQ improperly shut down, performing recover, this may take some time."
> Before recovery will be helpful for users trying to figure out what's happening in production.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)