| Author |
Message
|
| Bichu |
 Posted: Mon Aug 08, 2016 2:21 am Post subject: Preprod and Prod cluster name |
 |
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
Hi Guys,
Is it a good practise to name the cluster name same in pre prod and prod. Or is it good to append environment name some thing like QA.CLUSTER and PROD.CLUSTER.
I am creating cluster for the first time. so not sure. But I think it will be good to append environment names to the cluster name.
What's your thought? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Aug 08, 2016 5:07 am Post subject: Re: Preprod and Prod cluster name |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Bichu wrote: |
| Is it a good practise to name the cluster name same in pre prod and prod. |
Depends how good you are at keeping queue managers apart and how good your cluster management is.
| Bichu wrote: |
| I think it will be good to append environment names to the cluster name. |
Especially for your first cluster, I'd be inclined to agree. See how well it works out for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bichu |
| Posted: Mon Aug 08, 2016 5:09 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 08, 2016 5:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Also make sure your queue managers have different names in production and preprod (and everywhere else). If you have any kind of error, you want to know immediately which qmgr is involved.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 08, 2016 5:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Also make sure your queue managers have different names in production and preprod (and everywhere else). |
The most obvious mistake to make with clusters, and the one that will break it fastest & most completely, is to have two queue managers with the same name in the same cluster.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bichu |
| Posted: Mon Aug 08, 2016 5:41 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
| Thanks Jeff. I have created the queue managers name appended with environment. |
|
| Back to top |
|
|
| Bichu |
| Posted: Mon Aug 08, 2016 5:45 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
| Vitor wrote: |
| mqjeff wrote: |
| Also make sure your queue managers have different names in production and preprod (and everywhere else). |
The most obvious mistake to make with clusters, and the one that will break it fastest & most completely, is to have two queue managers with the same name in the same cluster. |
I understood vitor.
So do cluster sender and channel names have any specific naming conventions bcz I can see the names started with TO.QMXXXX and TO.QMYYYY when I created a cluster using MQ Explorer. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 08, 2016 5:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Bichu wrote: |
| So do cluster sender and channel names have any specific naming conventions bcz I can see the names started with TO.QMXXXX and TO.QMYYYY when I created a cluster using MQ Explorer. |
Cluster sender/receiver channels have to have the same names to match up just like non-clustered sender/receiver channels. The TO.<queue manager name> convention is the standard one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bichu |
| Posted: Mon Aug 08, 2016 5:58 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
|
| Back to top |
|
|
| exerk |
| Posted: Mon Aug 08, 2016 8:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Another convention is QMGR.CLUSTER, e.g. QM01.CLUS1, which can be useful where queue managers are in more than one cluster and you want to easily identify which channel is for which cluster. IMHO, it is not a good idea to namelist CLUSRCVR channels.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Aug 08, 2016 4:01 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2494
Location: Melbourne, Australia
|
Cluster names should indicate the environment and contain a serial number so that you can have more than 1 cluster in each environment. Eg. CLUSTER.QA01, CLUSTER.PROD01
Cluster receiver channels should contain a cluster name indicator so that a qmgr can be in more than 1 cluster (but not overlapping QA and PROD - always keep them separate). Qmgr names should also contain a serial. Eg.
TO.QA01.MYQM01QA
TO.PROD01.MYQM01PROD
Bear in mind that chl names are limited to 20 chars.
Some shops only use 1 char to indicate the environment, Eg. D, T, Q, P.
YMMV.
_________________
Glenn |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Aug 09, 2016 1:08 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
To save 3 characters when you only have 20 to use, some shops do not use the TO. at the beginning. If every cluster channel you make was going to have TO. at the start, you can eliminate it, and just pretend its there. Saves 3 valuable characters.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Aug 10, 2016 2:42 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
So... if you think about it, your Qmgr name should not be longer than 9 characters and your cluster name should not be longer than 9 characters because when you combine them to make a channel, you will end up with 19 characters if you separate them with a dot '.' character and that leaves you with one more character for a number should you need it for some reason.
Consider:
<ClusterName>.<QmgrName>n for cluster channel names
And
<FromQmgrName>.<ToQmgrName> for non cluster channel names
Further more name your Qmgr something like
ABBBCCCDE
Where A=environment (P=Prod, Q=QA,D=Dev) (imho the environment is the most important thing to know when you get paged at 2AM)
B=Owner (some three letter code)
C=Function (IIB, APP or something that makes sense to you)
D=0..9 for horizontal scaling
E=0..9 for vertical scaling
Do a similar thing for Cluster names... |
|
| Back to top |
|
|
|
|
