|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Another Interesting question |
« View previous topic :: View next topic » |
Author |
Message
|
jeevan |
Posted: Tue Apr 15, 2008 8:43 am Post subject: Another Interesting question |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
I am buidling a mq cluster. I have both full repositories ready and am adding partial repository one by one. One of the repositories queue manager is made a primary ( where the all PRs are connected via clussdr channels).
when I added a PR, both Primary FR and secondary FR see that queue manager. I mean when I do
dis clusqmgr(*), display all the queue manager. Also, I am watching in explorer. Also, as the test, I put a message to a cluster queue.
At one point, when I added a PR, it is seen by primary FR, but not by secondary FR. I can still put the message to a cluster queue.
I could not find any thing. Log is clean. No FDCs. I then deleted ( reset, stopped, deleted) and recreated, using the same script but still that particular queue manager is not seen by secondary FR.
I have not done anything different in other queue managers which were seen by secondary FR.
Can some one shedlight on this? |
|
Back to top |
|
 |
kevinQ |
Posted: Tue Apr 15, 2008 9:52 am Post subject: |
|
|
Novice
Joined: 09 Apr 2008 Posts: 21
|
try refresh cluster on the other full repository qmgr, if I understood what you were talking about.
You used some terms I am not farmiliar with, like the "primary" full repository? What is that? Is that the qmgr to which you define the CLUSSDR channel on other qmgrs? Also it took me a while to figure out what you meant by "adding partial repository one by one". That meant you were adding qmgrs to the cluster one by one, right? |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 15, 2008 9:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
No reason to ever run refresh cluster, in general.
Just wait a bit, and the cluster will take care of itself. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
kevinQ |
Posted: Tue Apr 15, 2008 10:21 am Post subject: |
|
|
Novice
Joined: 09 Apr 2008 Posts: 21
|
jefflowrey wrote: |
No reason to ever run refresh cluster, in general.
Just wait a bit, and the cluster will take care of itself. |
If you are patient
We did run into situations the queues hosted on a qmgr became unavailable for no known reason, and we had to refresh cluster to get it back in. But you were right, very rarely ... |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 15, 2008 10:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
kevinQ wrote: |
If you are patient |
Which would you rather wait for? the next normal cluster refresh interval to pass?
Or for all of your cluster channels to quiesce and restart, and then republish all of the information about their queue manager?
Also, when it comes to any kind of administration... and this is at least triply-so of MQ cluster administration... patience is your best virtue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jeevan |
Posted: Tue Apr 15, 2008 12:06 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
jefflowrey wrote: |
kevinQ wrote: |
If you are patient |
Which would you rather wait for? the next normal cluster refresh interval to pass?
Or for all of your cluster channels to quiesce and restart, and then republish all of the information about their queue manager?
Also, when it comes to any kind of administration... and this is at least triply-so of MQ cluster administration... patience is your best virtue. |
In fact, I waited for a while. In fact, that was done last night. When I saw this monring, it was not seem from lets say FR B. I checked that with my college.
However, it is shown now. I took unusual time. Anyway, thank you for your input. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Apr 15, 2008 1:23 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
kevinQ wrote: |
jefflowrey wrote: |
No reason to ever run refresh cluster, in general.
Just wait a bit, and the cluster will take care of itself. |
If you are patient
We did run into situations the queues hosted on a qmgr became unavailable for no known reason, and we had to refresh cluster to get it back in. But you were right, very rarely ... |
Another trick to "wake up" a queue that seems to have gone missing is to change something on the q def on the PR to let the FR know. I like adding a period to the Queue Description field. That's enough to have the PR send the FR info about the q.
Haven't had to do this since MQ 5.3 CSD 4 or 5. Either the newer versions of MQ are better at clustering or I'm better at clustering. Probably a little of both. _________________ Peter Potkay
Keep Calm and MQ On |
|
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
|
|
|
|