[
https://issues.apache.org/jira/browse/GUACAMOLE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357263#comment-16357263
]
Kris Keller commented on GUACAMOLE-322:
---------------------------------------
We use DNS + NGINX for this. NGINX http and stream(tcp) directives support
most of what your asking for. If you need more special use cases then you
could consider integration lua script with NGINX (or install openresty) and
that will get you the ability to do all sorts of fancy logic like look up
routes in DB.
> Implement Additional Load Balancing Algorithms
> ----------------------------------------------
>
> Key: GUACAMOLE-322
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-322
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Reporter: Nick Couchman
> Assignee: Nick Couchman
> Priority: Minor
>
> Now that the connection_weight field has been added, it makes sense to build
> out support for additional load balancing algorithms for the BALANCING
> connection group and allow users to choose which algorithm to use.
> Guacamole currently supports Weighted Least Connection (and Least Connection,
> when weights are undefined or are equal). I propose adding support for the
> following:
> - Round Robin
> - Weighted Round Robin
> - Least Recently Used
> - Weighted Least Recently Used
> For (Weighted) Round Robin, the plan would be to look at all the connections
> in a group, order them by their id, and then have a DB field keep track of
> either the last one used or the next one to use (opinions?).
> For (Weighted) Least Recently Used, it should be relatively easy to look at
> the connection history table and grab the oldest start_date field for a list
> of connections in the group, then calculate out from there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
