[
https://issues.apache.org/jira/browse/ACE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777246#comment-13777246
]
Bram de Kruijff commented on ACE-380:
-------------------------------------
Configuring multiple serverURLs was implemented under ACE-379. The (default)
DiscoveryHandler will use these in order and (if not disabled) check if it can
connect to them before returning. Thus if 2 serverURLs are configured the first
will be used as long as it is available. Once the first become unavailable it
tries the second etc.
Two notes:
* This allows load of a large set of agents to be balanced by configuration. It
is not a round-robin implementation per agent.
* This only checks if a serverURL can be connected to. It does not
check/interpret statuscodes (eg. the "too busy".
Thus the default implementation does not cover "if the first is busy, go on to
the next", a custom DiscoveryHandler could. Should we incorporate some
checking/interpreting of statuscode in the check? I am not convinced.
WDYT? [~marrs] [~jajans]
> Make the management agent work with multiple URLs.
> --------------------------------------------------
>
> Key: ACE-380
> URL: https://issues.apache.org/jira/browse/ACE-380
> Project: ACE
> Issue Type: Improvement
> Components: Discovery, Management Agent
> Reporter: Marcel Offermans
> Assignee: Bram de Kruijff
>
> In ACE-379 multiple URLs are introduced. The management agent specifically
> should support using those and contacting them using some simple algorithm
> (ie: if the first is busy, go on to the next).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
