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 14:53:16 GMT
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

> 
> And the logs on backup server:
> 2014-05-25 18:19:54 [HA] debug amq.failover created.
> 2014-05-25 18:19:54 [HA] debug Backup starting, rejecting client connections.
> 2014-05-25 18:19:54 [HA] info Membership: 66f38d8c(joining) 
> 2014-05-25 18:19:54 [HA] info Status change: standalone -> joining
> 2014-05-25 18:19:54 [HA] notice Initializing HA broker: 66f38d8c(joining)
> 2014-05-25 18:19:54 [HA] info Membership: 66f38d8c(joining) 
> 2014-05-25 18:19:54 [HA] info Backup: Brokers URL set to: amqp:tcp:qpid1:5672
> 2014-05-25 18:19:54 [HA] info Backup: Connecting to cluster, broker URL: amqp:tcp:qpid1:5672
> 2014-05-25 18:19:54 [HA] debug Status check amqp:tcp:qpid1:5672: active
> 2014-05-25 18:19:54 [HA] info Status check amqp:tcp:qpid1:5672: Joining established cluster
> 2014-05-25 18:19:56 [HA] debug Backup: Accepted admin connection: qpid.127.0.0.1:5672-127.0.0.1:44233
> 2014-05-25 18:20:00 [HA] debug Backup: Accepted admin connection: qpid.127.0.0.1:5672-127.0.0.1:44234
> 2014-05-25 18:20:01 [HA] debug Backup: Accepted admin connection: qpid.127.0.0.1:5672-127.0.0.1:44235
> 2014-05-25 18:20:02 [HA] debug Backup: Accepted admin connection: qpid.127.0.0.1:5672-127.0.0.1:44236
> 2014-05-25 18:20:14 [HA] debug Backup: Accepted admin connection: qpid.127.0.0.1:5672-127.0.0.1:44237
> 2014-05-25 18:20:15 [HA] info Backup: Brokers URL set to: amqp:tcp:qpid1:5672
> 2014-05-25 18:20:15 [HA] debug Status check amqp:tcp:qpid1:5672: active
> 2014-05-25 18:20:15 [HA] info Status check amqp:tcp:qpid1:5672: Joining established cluster
> 
> 
> 
> Why the backup host is unknow for master?
> Am I missing something obvius again?
> What is the Primary::closed state mean in qpid/ha/Primary.cpp?
> 
> 
> Thanks,
> Radek
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> 



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


Mime
View raw message