| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Clustering MQSeries vs Hardware Clustering |
« View previous topic :: View next topic » |
| Author |
Message
|
| vjsony |
 Posted: Fri Apr 18, 2003 2:34 am Post subject: Clustering MQSeries vs Hardware Clustering |
 |
|
Apprentice
Joined: 01 Aug 2001
Posts: 45
|
Hi,
Could someone tell me when do we go for MQSeries Clustering ? and when do we decide for Hardware Clustering of MQSeries?
Are there any drawbacks of MQSeries Clustering with V5.1? Is it alright to consider this configuration for a production environment.
Are there any scripts that are available for hardware clustering , particular to the Tru64 environment.
Do reply.
regards
VJ |
|
| Back to top |
|
 |
| gward123 |
| Posted: Sat Apr 26, 2003 12:02 pm Post subject: |
|
|
Novice
Joined: 27 Mar 2003
Posts: 11
Location: Roseland, NJ
|
Well, this depends on what you want to achieve....
A full 7x24 implementation of your MQ environment with minimal outages/disruptions would actually use both "technologies". But this also requires that your applications can "tolerate" an MQ cluster. So really there's two things:
1. MQ Clustering allows you to run multiple instances of your application. Care must be taken to understand any affinities that exist before you simply clone things and put them in an MQ cluster. Messages can be sent to any queue manager that hosts a clustered application queue. But once messages arrive, they can't be moved. People use MQ clusters to allow queue managers to be backed up and/or maintained without affecting the applications putting messages. It also makes "distributed queuing" much easier with fewer objects.
2. HA clustering allows you to pick up a failed queue manager and continue processing with a small delay (usually about 2 minutes of outage). So, if you lost a CPU or network connectivity to a specific box, the HA software will move resources to another machine for processing. The issue here is that damage to the shared disk (i.e., the queue file system or logs are damaged due to malicious or non-malicious actions and that damage is mirrored) will cause an outage since moving to another processor won't fix this problem.
Of course, there's other issues as well... more than can be covered here. But this is a start... others I'm sure will chime in!
Regards,
Gary
_________________
Gary J. Ward
Sr. Technical Consultant
ADP |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
