[
https://issues.apache.org/jira/browse/QPID-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677143#comment-13677143
]
James Belch commented on QPID-4910:
-----------------------------------
Thanks for the quick response. I think we will to configure the clients with a
list of brokers for the non Java clients. Could you guys answer another
question for me regarding failover. I am using Berkeley DB to implement our
High Availability solution. I have the master configured as follows:
<name>localhost</name>
<localhost>
<store>
<class>org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore</class>
<environment-path>${work}/bdbhastore/host1</environment-path>
<highAvailability>
<groupName>ReplicationGroup</groupName>
<nodeName>host1</nodeName>
<nodeHostPort>host1:5001</nodeHostPort>
<helperHostPort>host1:5002</helperHostPort>
<durability>NO_SYNC\,NO_SYNC\,SIMPLE_MAJORITY</durability>
<coalescingSync>true</coalescingSync>
<designatedPrimary>true</designatedPrimary>
</highAvailability>
</store>
...
</localhost>
I have the replica configured as follows:
<name>localhost</name>
<localhost>
<store>
<class>org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore</class>
<environment-path>${work}/bdbhastore/host2</environment-path>
<highAvailability>
<groupName>ReplicationGroup</groupName>
<nodeName>host2</nodeName>
<nodeHostPort>host2:5001</nodeHostPort>
<helperHostPort>host1:5002</helperHostPort>
<durability>NO_SYNC\,NO_SYNC\,SIMPLE_MAJORITY</durability>
<coalescingSync>true</coalescingSync>
<designatedPrimary>false</designatedPrimary>
</highAvailability>
</store>
...
</localhost>
When I start the replica server, I get the following error: "New node host2(-1)
unknown to rep group".
If I do a netstat, I see the connections attempting to be made, but the sockets
go to TIME_WAIT state and timeout after a minute. Any ideas?
> Python, Ruby, and C++ clients automatically connect to replica server when
> master fails
> ---------------------------------------------------------------------------------------
>
> Key: QPID-4910
> URL: https://issues.apache.org/jira/browse/QPID-4910
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.20
> Environment: C++, Ruby, Python, and Java clients connecting to a Java
> Broker running on Redhat 6.3
> Reporter: James Belch
> Fix For: 0.23
>
>
> I am currently in the process of designing a high availability solution for
> our software. We are using the Java broker, and we have Java, Ruby, C++, and
> Python clients. I was reading your High Availability document at
> http://qpid.apache.org/books/0.18/AMQP-Messaging-Broker-Java-Book/html/High-Availability.html
> and saw a footnote at the bottom stating "[1] The automatic failover feature
> is available only for AMQP connections from the Java client. Management
> connections (JMX) do not current offer this feature." Is this still the case
> or was this fixed in .20? If this is still the case, will it be fixed in a
> future release?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
