HornetQ HA mode

[ryuyan]

Hi,

I am tring HornetQ HA mode using shared store recently and found two interesting scenarios:

1. I configured the both two nodes as live, the second will become backup automatically.

2. Without making two nodes  a pair of live/backup using clustering, both are live, the second live is keeping trying to get live lock and when if first node is down, it becomes live automatically.

Can I say as along as we use shared store between multiple nodes, it's kind of HA mode?

Thanks.

Yan

[gaohoward]

mind uploading your node configurations?

[ryuyan]

1. logs of scenario 1:

11:36:10,106 INFO  [org.hornetq.integration.bootstrap] HQ101000: Starting Hornet

Q Server

11:36:11,993 WARN  [org.hornetq.core.server] HQ222018: AIO was not located on th

is platform, it will fall back to using pure Java NIO. If your platform is Linux

, install LibAIO to enable the AIO journal

11:36:12,180 INFO  [org.hornetq.core.server] HQ221000: live server is starting w

ith configuration HornetQ Configuration (clustered=true,backup=false,sharedStore

=true,journalDirectory=D:\hornetq-2.3.0.Final\data\journal,bindingsDirectory=D:\

hornetq-2.3.0.Final\data\bindings,largeMessagesDirectory=D:\hornetq-2.3.0.Final\

data\large-messages,pagingDirectory=D:\hornetq-2.3.0.Final\data\paging)

11:36:12,180 INFO  [org.hornetq.core.server] HQ221006: Waiting to obtain live lo

ck

11:36:12,570 INFO  [org.hornetq.core.server] HQ221013: Using NIO Journal

11:36:12,586 WARN  [org.hornetq.core.server] HQ222007: Security risk! HornetQ is

running with the default cluster admin user and default password. Please see th

e HornetQ user guide, cluster chapter, for instructions on how to change this.

11:36:16,582 INFO  [org.hornetq.core.server] HQ221031: backup announced

11:36:17,861 INFO  [org.hornetq.core.server] HQ221034: Waiting to obtain live lo

ck

11:36:37,392 WARN  [org.hornetq.core.client] HQ212037: Connection failure has be

en detected: HQ119015: The connection was disconnected because of server shutdow

n [code=DISCONNECTED]

11:36:37,938 INFO  [org.hornetq.core.server] HQ221035: Live Server Obtained live

lock

11:36:42,618 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.exampleQueue

11:36:42,665 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.DLQ

11:36:42,681 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.ExpiryQueue

11:36:42,852 INFO  [org.hornetq.core.server] HQ221020: Started Netty Acceptor ve

rsion 3.6.2.Final-c0d783c 192.168.0.105:5456 for CORE protocol

11:36:42,868 INFO  [org.hornetq.core.server] HQ221020: Started Netty Acceptor ve

rsion 3.6.2.Final-c0d783c 192.168.0.105:5446 for CORE protocol

11:36:42,883 WARN  [org.hornetq.core.client] HQ212034: There are more than one s

ervers on the network broadcasting the same node id. You will see this message e

xactly once (per node) if a node is restarted, in which case it can be safely ig

nored. But if it is logged continuously it means you really do have more than on

e node on the same network active concurrently with the same node id. This could

occur if you have a backup node active at the same time as its live node. nodeI

D=e60a078c-ffd5-11e2-a88e-7f1c561a1667

11:36:42,915 INFO  [org.hornetq.core.server] HQ221007: Server is now live

11:36:42,915 INFO  [org.hornetq.core.server] HQ221001: HornetQ Server version 2.

3.0.SNAPSHOT (colonizer, 123) [e60a078c-ffd5-11e2-a88e-7f1c561a1667]

2. logs of scenario 2

11:38:07,080 INFO  [org.hornetq.integration.bootstrap] HQ101000: Starting Hornet

Q Server

11:38:09,264 WARN  [org.hornetq.core.server] HQ222018: AIO was not located on th

is platform, it will fall back to using pure Java NIO. If your platform is Linux

, install LibAIO to enable the AIO journal

11:38:09,591 INFO  [org.hornetq.core.server] HQ221000: live server is starting w

ith configuration HornetQ Configuration (clustered=false,backup=false,sharedStor

e=true,journalDirectory=D:\hornetq-2.3.0.Final\data\journal,bindingsDirectory=D:

\hornetq-2.3.0.Final\data\bindings,largeMessagesDirectory=D:\hornetq-2.3.0.Final

\data\large-messages,pagingDirectory=D:\hornetq-2.3.0.Final\data\paging)

11:38:09,607 INFO  [org.hornetq.core.server] HQ221006: Waiting to obtain live lo

ck

11:38:10,153 INFO  [org.hornetq.core.server] HQ221013: Using NIO Journal

11:38:10,184 WARN  [org.hornetq.core.server] HQ222007: Security risk! HornetQ is

running with the default cluster admin user and default password. Please see th

e HornetQ user guide, cluster chapter, for instructions on how to change this.

11:38:15,380 INFO  [org.hornetq.core.server] HQ221034: Waiting to obtain live lo

ck

11:38:17,439 INFO  [org.hornetq.core.server] HQ221035: Live Server Obtained live

lock

11:38:21,995 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.exampleQueue

11:38:22,042 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.DLQ

11:38:22,042 INFO  [org.hornetq.core.server] HQ221003: trying to deploy queue jm

s.queue.ExpiryQueue

11:38:22,370 INFO  [org.hornetq.core.server] HQ221020: Started Netty Acceptor ve

rsion 3.6.2.Final-c0d783c 192.168.0.105:5446 for CORE protocol

11:38:22,370 INFO  [org.hornetq.core.server] HQ221020: Started Netty Acceptor ve

rsion 3.6.2.Final-c0d783c 192.168.0.105:5456 for CORE protocol

11:38:22,385 INFO  [org.hornetq.core.server] HQ221007: Server is now live

11:38:22,385 INFO  [org.hornetq.core.server] HQ221001: HornetQ Server version 2.

3.0.SNAPSHOT (colonizer, 123) [e60a078c-ffd5-11e2-a88e-7f1c561a1667]

[ataylor]

moved to correct forum