[
https://issues.apache.org/jira/browse/CAMEL-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623597#comment-14623597
]
Claus Ibsen commented on CAMEL-3910:
------------------------------------
Maybe we should improve the failover LB to make a few more options
- strategy = restart | round-robin | stricky |
Today we only have restart and round-robin. So if we make that roundrobin
option as deprecated and then an enum with different choices.
> Add "Sticky Failover" support in the camel load balancer
> --------------------------------------------------------
>
> Key: CAMEL-3910
> URL: https://issues.apache.org/jira/browse/CAMEL-3910
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Ashwin Karpe
>
> Essentially, given a list of endpoints (endpoint1, endpoint2), the
> failoverpolicy should initially send all messages to endpoint1. In a failover
> scenario, the route should send messages to endpoint2 instead of endpoint1,
> and continue to do so until endpoint2 fails. If endpoint2 were then to fail,
> messages start being sent to endpoint1 again.
> The current support for sticky load balancing and failover load balancing do
> not address the need for sticky failover.
> Sticky Load Balancing requires the user to set a header and is not meant for
> failover scenarios, whereas failover load balancing is not sticky.
> Please check out the following Nabble link for more details
>
> http://camel.465427.n5.nabble.com/Sticky-failover-load-balancing-td4346193.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
