You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/06/27 04:00:00 UTC

[jira] [Resolved] (GUACAMOLE-317) Allow for failover-only connections

     [ https://issues.apache.org/jira/browse/GUACAMOLE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper resolved GUACAMOLE-317.
--------------------------------------
       Resolution: Done
    Fix Version/s: 0.9.14-incubating

> Allow for failover-only connections
> -----------------------------------
>
>                 Key: GUACAMOLE-317
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-317
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-jdbc
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.14-incubating
>
>
> Particularly in light of recent changes implementing connection failover (GUACAMOLE-267), it's become clear that balancing group order needs to be predictably (and configurably) deterministic.
> A good portion of that requirement is achieved via GUACAMOLE-102, which allows connections to be weighted, however:
> Consider the case where a balancing group contains several connections, which are meant to be used only when other connections are unavailable (a [hot spare|https://en.wikipedia.org/wiki/Hot_spare]). As currently implemented, such a balancing group will always distribute load evenly across its connections (or at least evenly with respect to weights), including the connections intended for failover only. Though GUACAMOLE-267 will cause the group to avoid failing connections, the backup connections will still be used in cases where no connections are failing.
> Somehow, balancing group policy needs to be configurable to the extent that underlying connections can be dedicated to backup/failover cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)