[
https://issues.apache.org/jira/browse/GUACAMOLE-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081604#comment-17081604
]
Jason Keltz commented on GUACAMOLE-1022:
----------------------------------------
Hi Nick. Although I would *love* Guacamole to check the status of individual
hosts, I understand why this would be difficult. However, load balanced groups
without having the ability to continue to the next connection are not very
useful as I discovered when the first host in a list of 78 was down.
There are other issues with load balanced groups that I would like to bring to
your attention as well. For example, to the user, there is no visual
difference between the appearance of an organizational group and a load
balanced group. Load balanced groups open up just like organization groups.
Unless the user knows that it's a load balanced group (and there's nothing to
tell them that it is), the user is more likely to just open up the group, and
select a host. Load balanced groups need to display differently to distinguish
themselves from organization groups. As an admin, I would also like an option
to not allow even allow opening the group. I'd like the user to see the group
name maybe followed by how many hosts total in the group, and how many in use
(ideally how many are down, but as per above, I know this isn't easy).
> 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)
