On 03/09/2015 11:54 AM, James A. Robinson wrote:
On Fri, Mar 6, 2015 at 6:07 AM, underflow <underf...@async.eu> wrote:
- Another idea was to create a network of brokers with the original instance
(w/ kahadb persistence) and the new instance (w/ leveldb persistence) +
resending all content, if required...
I'll be curious to see what advice you get. I'm new to activemq, but this
sounds like a very reasonable approach to me. I'd set up a cluster with
the new backing store and migrate clients to it. Once I was happy the old
one is not needed I'd turn off the transport connectors and let it forward
any remaining data to the new cluster.
Jim
This is in fact a reasonable solution. This is also recommended when
upgrading brokers even when using KahaDB so that messages from an older
KahaDB version can be drained to the new broker.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
