[
https://issues.apache.org/jira/browse/GUACAMOLE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Keltz updated GUACAMOLE-1022:
-----------------------------------
Comment: was deleted
(was: I tried again with slightly different result...
1) I unchecked the internal hosts on the balanced group. I stopped xrdp on
host01. I tried to connect to the balanced group as a user. I was connected
to host02. Great. That's not what happened before, but it's what you said
should have happened.
2) I then stopped xrdp on host02 to simulate a machine crash. Because I have
session affinity enabled, when the user clicks on the balanced group, he gets
an error about being unable to connect. Yes, I have session affinity enabled,
but even if session affinity is enabled, if the system the user is connecting
to is no longer available, I'd still want the user to get another connection.
It seems like an additional admin option is necessary – enable/disable session
affinity, and maybe a failover option.
3) I turned off session affinity, and tried to connect and the user was
connected to host03. Great. However, here's the weird part. As an admin on a
different machine, I clicked on the load balanced group, and it reported to the
admin: "This connection is currently in use, and concurrent access to this
connection is not allowed. Please try again later.". Huh? I logged out as the
user, and now when the admin clicks on the balanced group, he was connected to
host03. However, when the user clicks on the balanced group, he now gets the
same error: "This connected is currently in use". In both cases, the user
should have been directed to host04. Something not quite right there.)
> 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)
