qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-1064) Doc link route reconnect behavior
Date Thu, 12 Jul 2018 15:00:00 GMT

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

ASF GitHub Bot commented on DISPATCH-1064:
------------------------------------------

Github user ted-ross commented on a diff in the pull request:

    https://github.com/apache/qpid-dispatch/pull/339#discussion_r202064815
  
    --- Diff: docs/books/user-guide/routing.adoc ---
    @@ -102,6 +102,17 @@ Link routing supports local transactions to a broker.
     +
     With a link route, consumers can provide server-side selectors for broker subscriptions.
     
    +[id='considerations-for-broker-connection-failure-handling']
    +=== Considerations for Broker Connection Failure Handling
    +
    +The message routing and link routing mechanisms both enable you to transfer messages
to brokers. However, they differ in how they behave if the connection to the broker is lost.
If you require the ability for the connection to be reestablished automatically, you should
use message routing (with autolinks).
    +
    +With link routing::
    +The client appears to be directly connected to the broker even though it is actually
connected to a router, which is link routed to the broker. If the broker goes offline, the
router sees the connection failure and closes all of the routed links that were attached to
the broker. The client's connection to the router, however, remains open. Therefore, the client
does not see the connection failure between the broker and the router and does not attempt
to reestablish it.
    --- End diff --
    
    I think this needs to be more explicit about what is routed and what is not.  When a broker
with link-routes goes offline, the routed links are detached.  The router will continue to
attempt to reconnect to the broker (or its backup) at which point, the link-routes will be
reactivated (i.e. they will become reachable again).
    
    The client does not see a dropped connection, but it does see the detached links (senders
and/or receivers).  The client has the option of attempting to re-attach lost links.  The
reattach will either go to a different broker, fail due to no available destination, or be
reattached to the original broker when it comes back online.


> Doc link route reconnect behavior
> ---------------------------------
>
>                 Key: DISPATCH-1064
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1064
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.2.0
>            Reporter: Ben Hardesty
>            Assignee: Ben Hardesty
>            Priority: Major
>
> When the router is configured with a linkRoute and client connects using failover, the
link will not be reestablished should the router's connection to the broker fail. If auto-reconnect
isĀ  required, the router should be configured with autoLink.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message