qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Conway <acon...@redhat.com>
Subject Re: [HA] debug Backup Rejected connection - problem with setting up qpid HA
Date Tue, 27 May 2014 18:20:30 GMT
On Tue, 2014-05-27 at 18:51 +0100, Radek Smigielski wrote:
> > On Tuesday, 27 May 2014, 15:53:50, Alan Conway <aconway@redhat.com> wrote:
> > > On Sun, 2014-05-25 at 23:33 +0100, Radek Smigielski wrote:
> >> 
> >>  > On Sunday, 25 May 2014, 21:51:39, Pavel Moravec 
> > <pmoravec@redhat.com> wrote:
> >>  > > Hi Radek,
> >>  > did you promote either of brokers to be a primary? See qpid-ha promote

> > command.
> >>  > 
> >>  > Kind regards,
> >>  > Pavel
> >> 
> >> 
> >>  Thanks Pavel, it does the trick, almost. Now one of my nodes becomes active

> > but the backup
> >>  one stays in "joining" state, never exits it. 
> >> 
> >>  This is what I see on master: 
> >>  [radek@qpid1 /]$ qpid-ha query
> >>  Status:              active
> >>  Brokers URL:         amqp:tcp:qpid2:5672
> >>  Public URL:
> >>  Expected Backups:    None
> >>  Replicate:           all
> >> 
> >>  And on master:
> >>  [HA] info Primary: Disconnect from unknown backup 66f38d8c(joining)
> >>             
> >> 
> >> 
> >>  And this is a backup node:
> >>  [radek@qpid2 ~]$ qpid-ha query
> >>  Status:              joining
> >>  Brokers URL:         amqp:tcp:qpid1:5672
> >>  Public URL:
> >>  Expected Backups:    None
> >>  Replicate:           all
> > 
> > Your brokers-url should be the same for all brokers, and should contain
> > a list of all the brokers in your cluster i.e: 
> > 
> > brokers-url: amqp:tcp:qpid1:5672,tcp:qpid2:5672
> > 
> 
> 
> I beleive you mean ha-broker-url option. I set it on both brokers to:
> 
> ha-brokers-url=amqp:tcp:qpid1:5672,tcp:qpid2:5672
> 
> 
> But still the backup broker stays in joining state:
> [radek@qpid1 ~]$  qpid-ha status --all
> qpid1:5672 active
> qpid2:5672 joining
> 
> 
> 
> I don't know if this matters but the master broker show this: 
> 
> 2014-05-27 13:49:03 [HA] info Primary: New backup connection: 3bc70754(joining)
> 2014-05-27 13:49:03 [HA] info Membership: 6732b428@tcp:qpid1:5672(active) 3bc70754(catchup)

> 2014-05-27 13:49:03 [HA] info Membership: 6732b428@tcp:qpid1:5672(active) 3bc70754(ready)

> 2014-05-27 13:49:03 [HA] info Primary: New backup is ready: 3bc70754(ready)
> 2014-05-27 13:49:03 [HA] info Primary: Disconnect from backup 3bc70754(joining)
> 2014-05-27 13:49:03 [HA] info Membership: 6732b428@tcp:qpid1:5672(active) 
> 2014-05-27 13:49:03 [HA] info Primary: Disconnect from unknown backup 3bc70754(joining)
> 
> 
> And the last line indicates that master broker still doesn't know the backup broker for
some reason?

That is odd. It shows the new backup actually becomes ready, but then
disconnects for some reason - and then appears to disconnect _again_,
which is why it is reported as unknown, because as far as the primary is
concerned it is not connected at that point. Hmm. Can you send me the
full logs from primary & backup please?  Use these flags:
  --log-enable=debug+:HA --log-enable=info+

Cheers,
Alan.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message