[
https://issues.apache.org/jira/browse/GUACAMOLE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082317#comment-17082317
]
Jason Keltz commented on GUACAMOLE-1022:
----------------------------------------
I tried again with slightly different result. After some experimentation, I'm
going to assume that the result was probably due to session affinity. If
session affinity is enabled, and the host the user was connected to is no
longer available, the user won't be able to connect to another host. A
sub-option of session affinity might allow the admin to allow the user to
switch host in the event of host failure ("session affinity failover" maybe).
> 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)
