[
https://issues.apache.org/jira/browse/GUACAMOLE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082929#comment-17082929
]
Mike Jumper commented on GUACAMOLE-1022:
----------------------------------------
I'm not sure that would make sense. The point of session affinity is to allow
the user to be routed to the same underlying connection due to some underlying
session state which must be maintained. In a situation where session affinity
is desired, isn't the best option to present the user with an error so that
they know their previous session is gone / temporarily unavailable due to a
failure? They can then decide whether to log off and give up, in which case
they'll be routed to a different machine next time, or to continue retrying in
the hopes that the failure is transient.
I would think that automatically failing over despite session affinity would be
confusing in the case of a true failure and dangerous in the case of a
transient failure.
> Allow load balancing groups to fail to next connection
> ------------------------------------------------------
>
> Key: GUACAMOLE-1022
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1022
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
> Reporter: Jason Keltz
> Priority: Minor
>
> I have 78 hosts in a balanced connection group. Let's say that the first
> host is down. Now, when the user click on the connection group expecting to
> get a connection, they instead get a message that Guacamole can't connect.
> If it can't connect to the first one, it should try the next one, then the
> next one until it finds one that works.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
