From commits-return-3653-apmail-ace-commits-archive=ace.apache.org@ace.apache.org Wed Sep 25 07:59:30 2013 Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DCB310BC3 for ; Wed, 25 Sep 2013 07:59:29 +0000 (UTC) Received: (qmail 87745 invoked by uid 500); 25 Sep 2013 07:59:27 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 87276 invoked by uid 500); 25 Sep 2013 07:59:18 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 87188 invoked by uid 99); 25 Sep 2013 07:59:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 07:59:13 +0000 Date: Wed, 25 Sep 2013 07:59:13 +0000 (UTC) From: "Bram de Kruijff (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACE-380) Make the management agent work with multiple URLs. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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