You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Prameet Patil <pr...@gmail.com> on 2021/02/02 05:37:47 UTC
KahaDB Migration in ActiveMQ 5.15.2
Hey guys,
We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB storage
mounted on a NFS server and we want to migrate this ActiveMQ cluster along
with kahaDB to a whole new different server without any downtime.
So our approach is to create a new ActiveMQ master-slave shared storage
cluster on the new servers and create a duplex network connector from old
broker to new broker, then make all the clients point to the new cluster.
now all the messages from old broker to new broker are brought on demand.
so we can keep the network connector for some time till all the messages
are forwarded from old broker to new broker,then remove the connector.
any issues in the above approach ??
and suggest if there are any better approaches.
Re: KahaDB Migration in ActiveMQ 5.15.2
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Yes, if you "reuse" one of the existing broker adding the network connector there, all messages will be forwarded to the new set, so no need to copy the kahadb folder.
Regards
JB
> Le 2 févr. 2021 à 07:21, Prameet Patil <pr...@gmail.com> a écrit :
>
> Ok thanks
> But why do we have to copy the kahaDB folder from the old broker to the new
> broker pair ???
> as anyway messages will be forwarded. is copying necessary ?
>
>
> On Tue, Feb 2, 2021 at 11:46 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> wrote:
>
>> Ah yes, ok.
>>
>> So, yeah, just add a new broker with a network connector (dynamic) to the
>> new pair.
>> Copy kahadb folder to the new pair and start the brokers.
>> Let the messages forwarded from the "front" broker to the pair.
>>
>> Regards
>> JB
>>
>>> Le 2 févr. 2021 à 07:12, Prameet Patil <pr...@gmail.com> a
>> écrit :
>>>
>>> I am not trying to update the ActiveMQ version, I want to keep the same
>>> version.
>>> i just want to move this ActiveMQ cluster along with kahaDB shared
>> storage
>>> to a new set of servers.
>>> Current setup -> (master-slave ActiveMQ 5.15.2 ) with kahaDB shared
>>> storage
>>> New Setup - > (Master-slave ActiveMQ 5.15.2) with kahaDB shared storage
>>> (this is different mount point on the new server)
>>>
>>> On Tue, Feb 2, 2021 at 11:25 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> You can update "live", by:
>>>>
>>>> - shutting down slave and update to latest ActiveMQ version. You start
>> the
>>>> slave (he’s still slave).
>>>> - you shut down master, the slave becomes the master
>>>> - you can update the "old" master to new version
>>>>
>>>> No need to create a new master/slave pair, just update the current one
>>>> live.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>> Le 2 févr. 2021 à 06:37, Prameet Patil <pr...@gmail.com> a
>>>> écrit :
>>>>>
>>>>> Hey guys,
>>>>> We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB
>> storage
>>>>> mounted on a NFS server and we want to migrate this ActiveMQ cluster
>>>> along
>>>>> with kahaDB to a whole new different server without any downtime.
>>>>> So our approach is to create a new ActiveMQ master-slave shared storage
>>>>> cluster on the new servers and create a duplex network connector from
>> old
>>>>> broker to new broker, then make all the clients point to the new
>> cluster.
>>>>> now all the messages from old broker to new broker are brought on
>> demand.
>>>>> so we can keep the network connector for some time till all the
>> messages
>>>>> are forwarded from old broker to new broker,then remove the connector.
>>>>>
>>>>> any issues in the above approach ??
>>>>> and suggest if there are any better approaches.
>>>>
>>>>
>>
>>
Re: KahaDB Migration in ActiveMQ 5.15.2
Posted by Prameet Patil <pr...@gmail.com>.
Ok thanks
But why do we have to copy the kahaDB folder from the old broker to the new
broker pair ???
as anyway messages will be forwarded. is copying necessary ?
On Tue, Feb 2, 2021 at 11:46 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> Ah yes, ok.
>
> So, yeah, just add a new broker with a network connector (dynamic) to the
> new pair.
> Copy kahadb folder to the new pair and start the brokers.
> Let the messages forwarded from the "front" broker to the pair.
>
> Regards
> JB
>
> > Le 2 févr. 2021 à 07:12, Prameet Patil <pr...@gmail.com> a
> écrit :
> >
> > I am not trying to update the ActiveMQ version, I want to keep the same
> > version.
> > i just want to move this ActiveMQ cluster along with kahaDB shared
> storage
> > to a new set of servers.
> > Current setup -> (master-slave ActiveMQ 5.15.2 ) with kahaDB shared
> > storage
> > New Setup - > (Master-slave ActiveMQ 5.15.2) with kahaDB shared storage
> > (this is different mount point on the new server)
> >
> > On Tue, Feb 2, 2021 at 11:25 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> > wrote:
> >
> >> Hi,
> >>
> >> You can update "live", by:
> >>
> >> - shutting down slave and update to latest ActiveMQ version. You start
> the
> >> slave (he’s still slave).
> >> - you shut down master, the slave becomes the master
> >> - you can update the "old" master to new version
> >>
> >> No need to create a new master/slave pair, just update the current one
> >> live.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 2 févr. 2021 à 06:37, Prameet Patil <pr...@gmail.com> a
> >> écrit :
> >>>
> >>> Hey guys,
> >>> We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB
> storage
> >>> mounted on a NFS server and we want to migrate this ActiveMQ cluster
> >> along
> >>> with kahaDB to a whole new different server without any downtime.
> >>> So our approach is to create a new ActiveMQ master-slave shared storage
> >>> cluster on the new servers and create a duplex network connector from
> old
> >>> broker to new broker, then make all the clients point to the new
> cluster.
> >>> now all the messages from old broker to new broker are brought on
> demand.
> >>> so we can keep the network connector for some time till all the
> messages
> >>> are forwarded from old broker to new broker,then remove the connector.
> >>>
> >>> any issues in the above approach ??
> >>> and suggest if there are any better approaches.
> >>
> >>
>
>
Re: KahaDB Migration in ActiveMQ 5.15.2
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Ah yes, ok.
So, yeah, just add a new broker with a network connector (dynamic) to the new pair.
Copy kahadb folder to the new pair and start the brokers.
Let the messages forwarded from the "front" broker to the pair.
Regards
JB
> Le 2 févr. 2021 à 07:12, Prameet Patil <pr...@gmail.com> a écrit :
>
> I am not trying to update the ActiveMQ version, I want to keep the same
> version.
> i just want to move this ActiveMQ cluster along with kahaDB shared storage
> to a new set of servers.
> Current setup -> (master-slave ActiveMQ 5.15.2 ) with kahaDB shared
> storage
> New Setup - > (Master-slave ActiveMQ 5.15.2) with kahaDB shared storage
> (this is different mount point on the new server)
>
> On Tue, Feb 2, 2021 at 11:25 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> wrote:
>
>> Hi,
>>
>> You can update "live", by:
>>
>> - shutting down slave and update to latest ActiveMQ version. You start the
>> slave (he’s still slave).
>> - you shut down master, the slave becomes the master
>> - you can update the "old" master to new version
>>
>> No need to create a new master/slave pair, just update the current one
>> live.
>>
>> Regards
>> JB
>>
>>> Le 2 févr. 2021 à 06:37, Prameet Patil <pr...@gmail.com> a
>> écrit :
>>>
>>> Hey guys,
>>> We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB storage
>>> mounted on a NFS server and we want to migrate this ActiveMQ cluster
>> along
>>> with kahaDB to a whole new different server without any downtime.
>>> So our approach is to create a new ActiveMQ master-slave shared storage
>>> cluster on the new servers and create a duplex network connector from old
>>> broker to new broker, then make all the clients point to the new cluster.
>>> now all the messages from old broker to new broker are brought on demand.
>>> so we can keep the network connector for some time till all the messages
>>> are forwarded from old broker to new broker,then remove the connector.
>>>
>>> any issues in the above approach ??
>>> and suggest if there are any better approaches.
>>
>>
Re: KahaDB Migration in ActiveMQ 5.15.2
Posted by Prameet Patil <pr...@gmail.com>.
I am not trying to update the ActiveMQ version, I want to keep the same
version.
i just want to move this ActiveMQ cluster along with kahaDB shared storage
to a new set of servers.
Current setup -> (master-slave ActiveMQ 5.15.2 ) with kahaDB shared
storage
New Setup - > (Master-slave ActiveMQ 5.15.2) with kahaDB shared storage
(this is different mount point on the new server)
On Tue, Feb 2, 2021 at 11:25 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> Hi,
>
> You can update "live", by:
>
> - shutting down slave and update to latest ActiveMQ version. You start the
> slave (he’s still slave).
> - you shut down master, the slave becomes the master
> - you can update the "old" master to new version
>
> No need to create a new master/slave pair, just update the current one
> live.
>
> Regards
> JB
>
> > Le 2 févr. 2021 à 06:37, Prameet Patil <pr...@gmail.com> a
> écrit :
> >
> > Hey guys,
> > We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB storage
> > mounted on a NFS server and we want to migrate this ActiveMQ cluster
> along
> > with kahaDB to a whole new different server without any downtime.
> > So our approach is to create a new ActiveMQ master-slave shared storage
> > cluster on the new servers and create a duplex network connector from old
> > broker to new broker, then make all the clients point to the new cluster.
> > now all the messages from old broker to new broker are brought on demand.
> > so we can keep the network connector for some time till all the messages
> > are forwarded from old broker to new broker,then remove the connector.
> >
> > any issues in the above approach ??
> > and suggest if there are any better approaches.
>
>
Re: KahaDB Migration in ActiveMQ 5.15.2
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi,
You can update "live", by:
- shutting down slave and update to latest ActiveMQ version. You start the slave (he’s still slave).
- you shut down master, the slave becomes the master
- you can update the "old" master to new version
No need to create a new master/slave pair, just update the current one live.
Regards
JB
> Le 2 févr. 2021 à 06:37, Prameet Patil <pr...@gmail.com> a écrit :
>
> Hey guys,
> We have a master-slave ActiveMQ 5.15.2 broker with shared kahaDB storage
> mounted on a NFS server and we want to migrate this ActiveMQ cluster along
> with kahaDB to a whole new different server without any downtime.
> So our approach is to create a new ActiveMQ master-slave shared storage
> cluster on the new servers and create a duplex network connector from old
> broker to new broker, then make all the clients point to the new cluster.
> now all the messages from old broker to new broker are brought on demand.
> so we can keep the network connector for some time till all the messages
> are forwarded from old broker to new broker,then remove the connector.
>
> any issues in the above approach ??
> and suggest if there are any better approaches.