You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/11/16 18:26:00 UTC

[jira] [Commented] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover

    [ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444717#comment-17444717 ] 

ASF subversion and git services commented on DISPATCH-2256:
-----------------------------------------------------------

Commit fc975f2738e64e80cfe9f8dc552000e9e438225a in qpid-dispatch's branch refs/heads/main from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=fc975f2 ]

DISPATCH-2287: Comment out switchover tests in system_tests_fallback_dest until DISPATCH-2256 is fixed


> edge router fallback links and addresses incorrect on interior failover
> -----------------------------------------------------------------------
>
>                 Key: DISPATCH-2256
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-2256
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 1.17.0
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Major
>             Fix For: 1.19.0
>
>
> Scenario:
> Configure an edge router with two separate interior connectors - one for router A and a standby for router B.
> Configure a route-container listener for a broker on the edge router.  Assign two fallback destination autolinks (1 in, 1 out) to the route container for address "foo".
> Start just the edge router:
>  * no links are active (expected).
>  * mgmt query for addresses show two "foo" addresses present:
>  ** MFfoo - the fallback address (no subscribers)
>  ** M0foo - the primary address (no subscribers)
> Now startup the broker and after the connection to the broker:
>  * On the edge router:
>  ** links:
>  *** id 5, out link to broker, owning address MFfoo
>  *** id 6, in link from broker, owning address M0foo
>  ** addresses:
>  *** MFfoo - one local subscriber
>  *** M0foo - no subscribers
> Now start router A.  Router A has been configured with an edge listener connection.  There is no inter-router connection configured for router B!  Once the connection is established:
>  * On the edge router:
>  ** links:
>  *** the two broker links (see above)
>  *** id 10, in link from router A, owning address MFfoo
>  *** id 11, out link to router A for M0foo
>  ** addresses:
>  *** MFfoo - one local subscriber
>  *** M0foo - no subscribers
>  * On Router A:
>  ** links:
>  *** id 6, out link to edge, owning address MFfoo
>  *** id 7, in link from edge, owning address M0foo
>  ** addresses:
>  *** MFfoo - one local subscriber
>  *** M0foo - no subscribers
> Now start router B, wait for the edge to establish a connection to it.  Since B is a standby interior for the edge there are no 'foo' related links or addresses on B as expected.  Remember router A and B are not directly connected.
>  
> Fail router A.  Wait for the edge to re-establish its proxy links to router B.  The following links/addresses related to foo are now:
>  * On the edge router:
>  ** links:
>  *** the two broker links
>  *** id 20, in link from router B, owning address MFfoo
>  ** addresses:
>  *** MFfoo - one local subscriber
>  *** M0foo - no subscribers
>  * On Router B:
>  ** links:
>  *** id 6, out link to edge, owning address MFfoo
>  ** addresses:
>  *** MFfoo - one local subscriber
> From the above we can see that after the failover to router B the edge router does not re-establish an outgoing link (subscription) for M0foo as it did when connected to router A.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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