ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral DiscussionAWS Strategy for IBM MQ Autoscaling

Post new topicReply to topic
AWS Strategy for IBM MQ Autoscaling View previous topic :: View next topic
Author Message
MQ_AGENT
PostPosted: Thu Feb 28, 2019 3:13 pm Post subject: AWS Strategy for IBM MQ Autoscaling Reply with quote

Newbie

Joined: 05 Feb 2016
Posts: 7

Hey all,

I am trying to implement Autoscaling in AWS (if the ec2-instance with Queue Manager goes down, AWS autoscaling would create a new ec2-instance).This is for a multi-instance setup

Approach followed :

1-Have an AMI with IBM MQ fresh installation.
2-Build 2 Instances with this AMI with /var/mqm as local/EBS volume.
3-Attach EFS at boot up time to the servers via a bootup script.
4-use EFS for MQ Log and DataDirectory
5-Add a bootup script with addmqinf command for the queue manager.

Thus, once the ec2-instance is built with AMI, the server would have IBM MQ installed, the EFS attached via bootup script at runtime and mqs.ini updated via bootup scritp with addmqinf command.

During any disaster, existing ec2-instances would be terminated and new ec2-instances would be created. The Queue Manager would be failed over as a part of server termination. Since the data and log directory is in EFS, strmqm -x <QM> would start the queue managers in the new servers.

Only issue I think of is that FDC files in the now terminated EC-Instances would be lost.

Can such a configuration cause any issues at MQ level ?
Back to top
View user's profile Send private message
liz72703
PostPosted: Fri Apr 19, 2019 7:41 am Post subject: AWS Strategy for IBM MQ Autoscaling Reply with quote

Newbie

Joined: 25 Apr 2018
Posts: 1

Just curious how this approach has been working out for you? (We are also looking at migrating some of our MQ servers to the cloud.)

Did you look at the "IBM MQ on AWS" Quick Start? IBM took a slightly different approach with it and did not bother with the MQ multi-instance capability and instead used AWS auto scaling group to spin up a new EC2 instance if the first one became unhealthy (with the persistent data on EFS).

Liz
Back to top
View user's profile Send private message
avasthisamar
PostPosted: Wed Apr 24, 2019 10:00 pm Post subject: AWS Strategy for IBM MQ Autoscaling Reply with quote

Newbie

Joined: 18 Apr 2019
Posts: 1

With the release of IBM MQ v9.1 (Long Term Support, released in v9.0.4 Continuous Delivery), IBM introduced Replicated Data Queue Managersa highly available solution for Linux platforms that uses three servers in a HA group, each with a queue manager
Back to top
View user's profile Send private message
dextermbmq
PostPosted: Sat May 18, 2019 2:11 am Post subject: Reply with quote

Acolyte

Joined: 26 Jul 2014
Posts: 52

I also tested the same configuration . AWS autoscaling takes some time to kick-in(~3-4 mins) and multi-instance does the failover in 40-50 sec usually. Combining the Auto-scaling and multi-instance features would be a good idea.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral DiscussionAWS Strategy for IBM MQ Autoscaling
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.