| Author |
Message
|
| bruce2359 |
 Posted: Mon Sep 15, 2014 8:42 am Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Clustering forum.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
 |
| bkiran2020 |
| Posted: Mon Sep 15, 2014 9:00 am Post subject: Re: CLuster workload balance |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| Vitor wrote: |
| bkiran2020 wrote: |
| I have not changed the CLWLUSEQ attribute. |
I didn't ask if you'd changed it, I asked what it was set to.
I don't see anything here that proves that you're not doing a bind on open. |
AMQ8409: Display Queue details.
QUEUE(TESTQ.TESTCLUS) TYPE(QLOCAL)
CLWLUSEQ(QMGR)
dis qmgr clwluseq
5 : dis qmgr clwluseq
AMQ8408: Display Queue Manager details.
QMNAME(QM1) CLWLUSEQ(LOCAL)
Iam not sure about your question on "bind on open." |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Sep 15, 2014 9:08 am Post subject: Re: CLuster workload balance |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| bkiran2020 wrote: |
AMQ8409: Display Queue details.
QUEUE(TESTQ.TESTCLUS) TYPE(QLOCAL)
CLWLUSEQ(QMGR)
dis qmgr clwluseq
5 : dis qmgr clwluseq
AMQ8408: Display Queue Manager details.
QMNAME(QM1) CLWLUSEQ(LOCAL) |
And what do you suppose CLWLUSEQ(LOCAL) tells the Qmgr to do?
If you change it, change it on the queue (well all instances of the cluster queue) and not the Qmgr. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Mon Sep 15, 2014 9:21 am Post subject: Re: CLuster workload balance |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| bkiran2020 wrote: |
| Vitor wrote: |
| bkiran2020 wrote: |
| I have not changed the CLWLUSEQ attribute. |
I didn't ask if you'd changed it, I asked what it was set to.
I don't see anything here that proves that you're not doing a bind on open. |
AMQ8409: Display Queue details.
QUEUE(TESTQ.TESTCLUS) TYPE(QLOCAL)
CLWLUSEQ(QMGR)
dis qmgr clwluseq
5 : dis qmgr clwluseq
AMQ8408: Display Queue Manager details.
QMNAME(QM1) CLWLUSEQ(LOCAL)
Iam not sure about your question on "bind on open." |
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 15, 2014 9:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Look at the file called 'amqsput.0.c'.
It contains the source for amqsput.
Look in the KC for MQOO_BIND_AS_Q_DEF
Determine what MQOO options amqsput presents. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 15, 2014 9:50 am Post subject: Re: CLuster workload balance |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkiran2020 wrote: |
| CLWLUSEQ(LOCAL) |
Bingo!
Or Bazinga! (for our younger viewers)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Sep 15, 2014 11:09 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
 Wud I say?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 15, 2014 11:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| JosephGramig wrote: |
| Wud I say? |
The same thing I said in my initial response.
We da men! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 15, 2014 12:23 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Keep in mind that there are tradeoffs in performance with CLWLUSEQ.
CLWLUSEQ(LOCAL) provides the best performance when the app is MQCONNected to the local qmgr - all flows are cross-memory - no network involvement.
CLWLUSEQ(ANY) allows for outbound messages to be spread among available queues on available qmgrs, but imposes network flows - which is usually not the best performance.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 15, 2014 12:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
Keep in mind that there are tradeoffs in performance with CLWLUSEQ.
CLWLUSEQ(LOCAL) provides the best performance when the app is MQCONNected to the local qmgr - all flows are cross-memory - no network involvement.
CLWLUSEQ(ANY) allows for outbound messages to be spread among available queues on available qmgrs, but imposes network flows - which is usually not the best performance. |
Also CLWLUSEQ(LOCAL) requires a gateway from outside the cluster, CLWLUSEQ(ANY) does not.
You pays your money, you takes your choice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Mon Sep 15, 2014 8:04 pm Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| Vitor wrote: |
| bruce2359 wrote: |
Keep in mind that there are tradeoffs in performance with CLWLUSEQ.
CLWLUSEQ(LOCAL) provides the best performance when the app is MQCONNected to the local qmgr - all flows are cross-memory - no network involvement.
CLWLUSEQ(ANY) allows for outbound messages to be spread among available queues on available qmgrs, but imposes network flows - which is usually not the best performance. |
Also CLWLUSEQ(LOCAL) requires a gateway from outside the cluster, CLWLUSEQ(ANY) does not.
You pays your money, you takes your choice. |
We need to set DEFBIND(NOTFIXED) or CLWLUSEQ(ANY) ? what is the difference |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 15, 2014 8:25 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkiran2020 wrote: |
| We need to set DEFBIND(NOTFIXED) or CLWLUSEQ(ANY) ? what is the difference |
DEFBIND(NOTFIXED) is a Cluster QLocal definition attribute value which tells the MQ clustering software that it may find another instance of a destination queue should the current queue becomes unavailable, BUT only if the MQPUTting application has specified BIND_AS_Q_DEF (bind as defined at the queue definition).
CLWLUSEQ(ANY) is a queue-manager definition attribute value - that is described here http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.con.doc/q082420_.htm
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dware |
| Posted: Mon Sep 15, 2014 11:01 pm Post subject: |
|
|
Novice
Joined: 18 Nov 2013
Posts: 13
|
| Quote: |
| We need to set DEFBIND(NOTFIXED) or CLWLUSEQ(ANY) ? what is the difference |
DEFBIND controls when a routing choice is made, CLWLUSEQ influences what the choice is.
DEFBIND is the default 'bind' type used by a putting application. The 'bind' behaviour determines whether each and every message that is put can be workload balanced/routed to a different instance of the cluster queue (NOTFIXED). Or if all the messages have to go to the same instance even if its availability changes (OPEN). And then there's even the possibility to do it based on a message group (GROUP).
However, this doesn't determine which instances of the cluster queue messages will be routed to, just when a different choice is made.
The attributes that control which instances of a cluster queue are chosen (whether it's when you first open the queue or for every put) are all the CLWL* attributes (and PUT).
Specifically, CLWLUSEQ comes into play when there is an instance of the cluster queue on the same queue manager as the putting application is connected to. If there is it often makes good sense from a performance point of view (at least for the queue manager) to send all the message there. However, if true workload balancing is required you can switch off that inbuilt preference by using CLWLUSEQ. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Tue Sep 16, 2014 5:04 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| bruce2359 wrote: |
| bkiran2020 wrote: |
| We need to set DEFBIND(NOTFIXED) or CLWLUSEQ(ANY) ? what is the difference |
DEFBIND(NOTFIXED) is a Cluster QLocal definition attribute value which tells the MQ clustering software that it may find another instance of a destination queue should the current queue becomes unavailable, BUT only if the MQPUTting application has specified BIND_AS_Q_DEF (bind as defined at the queue definition).
CLWLUSEQ(ANY) is a queue-manager definition attribute value - that is described here http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.con.doc/q082420_.htm |
thanks
can we achieve workload without setting the CLWLUSEQ(ANY) attribute |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Sep 16, 2014 5:22 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| Not if you connect to a Qmgr hosting the cluster queue. You can if you connect to a 'gateway Qmgr' (a Qmgr that does not host an instance of the cluster queue). |
|
| Back to top |
|
|
|
|
