activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: replicated leveldb and scheduled messages…is it being worked on?
Date Wed, 30 Jul 2014 22:07:59 GMT
Ah… nice. I'll take a look at it. I was thinking about it this morning and
this is probably more complicated than it initially seems.

Logically it's somewhat straight forward, but there are a lot of steps
involved.  Lots of moving parts.

So what I will probably do is try to get this code in production… and when
we're ready to allocate a week or so to building this out, I'll post a
proposal to the list for an implementation strategy.




On Tue, Jul 29, 2014 at 7:07 PM, Timothy Bish <tabish121@gmail.com> wrote:

> On 07/29/2014 09:06 PM, Kevin Burton wrote:
>
>> Just looking at it now… I think what might be interesting is writing a
>> JobSchedulerStore without persistence and just using java.util.concurrent
>> collections interfaces…
>>
>> Just to prove that the semantics work and as a template for future
>> versions.  Then use that to get the LevelDB version to work.
>>
>
> Refer to InMemoryJobSchedulerStore.java on trunk for an scheduler store
> without persistence.
>
>
>> On Tue, Jul 29, 2014 at 5:30 PM, Kevin Burton <burton@spinn3r.com> wrote:
>>
>>  OK… I assume the current one is based on KahaDB?
>>>
>>>
>>> On Tue, Jul 29, 2014 at 4:42 PM, Timothy Bish <tabish121@gmail.com>
>>> wrote:
>>>
>>>  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
>>>>> <http://activemq.apache.org/delay-and-schedule-message-delivery.html>.
>>>>>
>>>>> Those are are stored in a separate non-replicated KahaDB data files.
>>>>> Unexpected results will occur if you use Delay and Schedule Message
>>>>> Delivery
>>>>> <http://activemq.apache.org/delay-and-schedule-message-delivery.html>
>>>>> 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.
>>>> tim.bish@redhat.com | www.fusesource.com | www.redhat.com
>>>> skype: tabish121 | twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>>>>
>>>>
>>> --
>>>
>>> Founder/CEO Spinn3r.com
>>> Location: *San Francisco, CA*
>>>
>>> blog: http://burtonator.wordpress.com
>>> … or check out my Google+ profile
>>> <https://plus.google.com/102718274791889610666/posts>
>>> <http://spinn3r.com>
>>>
>>>
>>>
>>
>
> --
> Tim Bish
> Sr Software Engineer | RedHat Inc.
> tim.bish@redhat.com | www.fusesource.com | www.redhat.com
> skype: tabish121 | twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>


-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message