[
https://issues.apache.org/jira/browse/QPID-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7025:
-----------------------------
Description:
Whilst investigating a failure of test
MultiNodeTest#testInFlightTransactionsWhilstMajorityIsLost I noticed that
Replica node was logging null application state which was received as part of
invocation of DbPing(r...)#getNodeState().
The log is below:
{noformat}
2016-01-27 17:05:07,569 BROKER-19 DEBUG
[Group-Change-Learner:test:nodetestInFlightTransactionsWhilstMajorityIsLost10007]
o.a.q.s.v.b.BDBHAVirtualHostNodeImpl Application state returned by JE was
'null' so skipping permitted node handling: Current state of node:
nodetestInFlightTransactionsWhilstMajorityIsLost10001 from group: test
Current state: MASTER
Current master: nodetestInFlightTransactionsWhilstMajorityIsLost10001
Current JE version: 5.0.104
Current log version: 8
Current transaction end (abort or commit) VLSN: 344
Current master transaction end (abort or commit) VLSN: 0
Current active feeders on node: 1
Current system load average: 58.23
{noformat}
The logs in the test log file indicate that after transition from MASTER into
DETACHED (after lost of majority) and back to MASTER after restoring full
cluster, the application state was not set on environment after flipping back
to MASTER.
It seems that information about permitted nodes is not communicated to replicas
was:
Whilst investigating a failure of test
MultiNodeTest#testInFlightTransactionsWhilstMajorityIsLost I noticed that
Replica node was logging null application state which was received as part of
invocation of DbPing(r...)#getNodeState().
The log is below:
{noformat}
2016-01-27 17:05:07,569 BROKER-19 DEBUG
[Group-Change-Learner:test:nodetestInFlightTransactionsWhilstMajorityIsLost10007]
o.a.q.s.v.b.BDBHAVirtualHostNodeImpl Application state returned by JE was
'null' so skipping permitted node handling: Current state of node:
nodetestInFlightTransactionsWhilstMajorityIsLost10001 from group: test
Current state: MASTER
Current master: nodetestInFlightTransactionsWhilstMajorityIsLost10001
Current JE version: 5.0.104
Current log version: 8
Current transaction end (abort or commit) VLSN: 344
Current master transaction end (abort or commit) VLSN: 0
Current active feeders on node: 1
Current system load average: 58.23
{noformat}
The logs in the test log file indicate that after transition from MASTER into
DETACHED (after lost of majority) and back to MASTER after restoring full
cluster, the application state was not set on environment after flipping back
to MASTER.
It seems that information about permitted nodes is not communicated to replicas
> [JavaBroker, BDB HA] Application state is not set on JE Node when BDB HA VHN
> role changes from MASTER to DETACHED and back to MASTER
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7025
> URL: https://issues.apache.org/jira/browse/QPID-7025
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0.1, qpid-java-6.1
> Reporter: Alex Rudyy
> Attachments:
> TEST-org.apache.qpid.server.store.berkeleydb.replication.MultiNodeTest.testInFlightTransactionsWhilstMajorityIsLost.txt
>
>
> Whilst investigating a failure of test
> MultiNodeTest#testInFlightTransactionsWhilstMajorityIsLost I noticed that
> Replica node was logging null application state which was received as part of
> invocation of DbPing(r...)#getNodeState().
> The log is below:
> {noformat}
> 2016-01-27 17:05:07,569 BROKER-19 DEBUG
> [Group-Change-Learner:test:nodetestInFlightTransactionsWhilstMajorityIsLost10007]
> o.a.q.s.v.b.BDBHAVirtualHostNodeImpl Application state returned by JE was
> 'null' so skipping permitted node handling: Current state of node:
> nodetestInFlightTransactionsWhilstMajorityIsLost10001 from group: test
> Current state: MASTER
> Current master: nodetestInFlightTransactionsWhilstMajorityIsLost10001
> Current JE version: 5.0.104
> Current log version: 8
> Current transaction end (abort or commit) VLSN: 344
> Current master transaction end (abort or commit) VLSN: 0
> Current active feeders on node: 1
> Current system load average: 58.23
> {noformat}
> The logs in the test log file indicate that after transition from MASTER into
> DETACHED (after lost of majority) and back to MASTER after restoring full
> cluster, the application state was not set on environment after flipping back
> to MASTER.
> It seems that information about permitted nodes is not communicated to
> replicas
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
