qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-5982) Stopped node viewed remotely reports stale replication transaction id
Date Mon, 25 Aug 2014 15:47:59 GMT

     [ https://issues.apache.org/jira/browse/QPID-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rob Godfrey updated QPID-5982:

    Fix Version/s:     (was: 0.31)

> Stopped node viewed remotely reports stale replication transaction id
> ---------------------------------------------------------------------
>                 Key: QPID-5982
>                 URL: https://issues.apache.org/jira/browse/QPID-5982
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.29
>            Reporter: Keith Wall
>            Assignee: Alex Rudyy
>            Priority: Minor
>              Labels: bdbstore, ha
>             Fix For: 0.30
> I have a HA group formed of three nodes. I stop one the nodes using the Stop button on
its VHN tab.  The node stops correctly and temporarily detaches from the group leaving the
two remaining nodes providing service.
> If I then observe the group from the VHN tab of either of the two remaining nodes, I
see the role of the stopped node as UNKNOWN (correct behaviour), but the replication transaction
id is still populated (with the last known value).  This information is stale and might mislead
the user.  In the case where the group has suffered a network partition the value could be
> A node should discard the remote replication transaction id when it looses contact with
the remote node and should display N/A.

This message was sent by Atlassian JIRA

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

View raw message