qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandy Pratt <prat...@adobe.com>
Subject RE: A few clustering/failover questions
Date Mon, 09 Mar 2009 18:06:06 GMT
I was attempting to rejoin the broker to the cluster, and found some errors in the logs.  This
snippet below seems to be where it starts:

2009-mar-09 10:53:47 trace 10.59.174.186:15159(DUMPEE) RECV 10.59.174.186:15159-0x8144690(local,catchup):
Frame[BEbe; channel=1; conte
nt (21 bytes) 55khagadlc-8yrlp...]
2009-mar-09 10:53:47 debug Exception constructed: Unexpected command start frame. (qpid/SessionState.cpp:57)
2009-mar-09 10:53:47 error Connection exception: framing-error: Unexpected command start frame.
(qpid/SessionState.cpp:57)
2009-mar-09 10:53:47 error Connection 10.59.174.211:49354 closed by error: Unexpected command
start frame. (qpid/SessionState.cpp:57)(
501)
2009-mar-09 10:53:47 trace 10.59.174.186:15159(DUMPEE) RECV 10.59.174.186:15159-0x8144690(local,catchup):
Frame[BEbe; channel=1; {Clus
terConnectionQueuePositionBody: queue=test.queue; position=19; }]
2009-mar-09 10:53:47 trace 10.59.174.186:15159(DUMPEE) RECV 10.59.174.186:15159-0x8144690(local,catchup):
Frame[Bbe; channel=1; {Messa
geTransferBody: destination=\x00qpid-dump\x00; accept-mode=1; acquire-mode=0; }]
2009-mar-09 10:53:47 debug Exception constructed: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:67)
2009-mar-09 10:53:47 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:67)
2009-mar-09 10:53:47 trace 10.59.174.186:15159(DUMPEE) RECV 10.59.174.186:15159-0x8144690(local,catchup):
Frame[be; channel=1; header
(99 bytes); properties={{MessageProperties: content-length=0; message-id=86fe821e-9123-3ef0-bb79-3ded7e79c767;
content-type=text/plain
; user-id=guest; }{DeliveryProperties: redelivered=1; priority=4; delivery-mode=2; timestamp=1236621013709;
expiration=0; exchange=tes
t.direct; routing-key=test.queue; }}]
2009-mar-09 10:53:47 debug Exception constructed: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:67)


The unexpected command start frame seems to be where it started.  Before that I see a bunch
of RECV lines and afterwards a bunch of "Channel 1 is not attached" errors.

Any idea what this means?



Thanks,

Sandy




-----Original Message-----
From: Carl Trieloff [mailto:cctrieloff@redhat.com] 
Sent: Wednesday, March 04, 2009 7:16 PM
To: users@qpid.apache.org
Cc: Sandy Pratt
Subject: Re: A few clustering/failover questions

Carl Trieloff wrote:
>
>>
>> Assume a cluster of two brokers, A and B
>> 1) A dies
>> 2) clients fail over to B
>> 3) do something to recover A without interrupting clients of B
>> 4) A and B are again interchangeable
>>
>> I've looked through the docs and haven't seen anything about this.  
>> Apologies if I missed it.  I also tried simply restarting A, which 
>> doesn't seem to work.
>>   
>
> Sandy,
>
> qpidd can support the hot joining of member back to the cluster. so 
> step 3 is simply.
>
> - rename or move the jrnl dir if you are running a durable store (if 
> no store skip this step)
> - restart node A with the same cluster-name as node B.
>
> It's that simple. What will happen is that the restarted node be will 
> be re-synced to the active state of node B, and you can continue on. 
> the clients will also be notified that
> the cluster-membership changes (Java & C++), so even if node B is 
> brought back on a different IP address the client will know where to 
> fail-over to.
>

Correction,  no rename of the jrnl dir is required, it will do that for 
you automatically.... just restart node A with the same cluster-name as 
node B.

It will do the rest for you...
Carl.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Mime
View raw message