activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiang Zhao (JIRA)" <>
Subject [jira] [Commented] (AMQ-6453) (Replicated)LevelDB becomes corrupt when under stress
Date Mon, 14 Nov 2016 14:35:59 GMT


Xiang Zhao commented on AMQ-6453:

I think it might be the same issue as  (which
is still open after 21 months)  or  
I'm using version 5.13.4, and had the similar issue: after fail over several times, I got
the error "No reader available for position" or "Invalid log position: 0 "
I suggest adding some warning on the related doc page,   "ReplicatedLevelDB is not ready for
production use". 

> (Replicated)LevelDB becomes corrupt when under stress
> -----------------------------------------------------
>                 Key: AMQ-6453
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store
>    Affects Versions: 5.14.0
>         Environment: OS: RHEL6; Virtual Machines (set of 3) 
>            Reporter: Michiel Lange
> When running ActiveMQ 5.14.0 in a set of 3 brokers with ReplicatedLevelDB, sending 100.000
messages with 100 threads (with jmeter) the persistency store becomes corrupt (becoming evident
when restarting a broker); Restarting a broker with "1" replicas allows the broker to be started
again and this seems to work to allow to start the broker again

This message was sent by Atlassian JIRA

View raw message