activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <>
Subject Re: replicated leveldb and scheduled messages…is it being worked on?
Date Tue, 29 Jul 2014 23:42:52 GMT
On 07/29/2014 07:19 PM, Kevin Burton wrote:
> So currently, the big caveat for leveldb replication is that replicating
> the schedule db doesn't work…
> How complicated is it going to be to get this to work with leveldb?
> Is anyone actively working on this?  I kind of painted myself into a corner
> on this one.  ActiveMQ does literally 95% of what I need and then I
> realized that this isn't going to work.
> If it's being fixed… that's great.  If not I  might need to step in and
> help out.
> The LevelDB store does not yet support storing data associated with Delay
> and Schedule Message Delivery
> <>.
> Those are are stored in a separate non-replicated KahaDB data files.
> Unexpected results will occur if you use Delay and Schedule Message Delivery
> <> with
> the replicated leveldb store since that data will be not be there when the
> master fails over to a slave.
There's no one currently working on this, we love contributions though.  
Trunk ActiveMQ has been updated to allow each of the persistence 
adapters to provide it's own implementation of JobSchedulerStore, so 
you'd need to implement one for LevelDB

Tim Bish
Sr Software Engineer | RedHat Inc. | |
skype: tabish121 | twitter: @tabish121

View raw message