Mailing-List: contact chukwa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@incubator.apache.org
Message-ID: <23394856.100791286908415144.JavaMail.jira@thor>
Date: Tue, 12 Oct 2010 14:33:35 -0400 (EDT)
From: "Bill Graham (JIRA)" <jira@apache.org>
To: chukwa-dev@incubator.apache.org
Subject: [jira] Created: (CHUKWA-534) Improve fault-tolerance of
 DemuxManager.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Improve fault-tolerance of DemuxManager.
----------------------------------------

                 Key: CHUKWA-534
                 URL: https://issues.apache.org/jira/browse/CHUKWA-534
             Project: Chukwa
          Issue Type: Improvement
            Reporter: Bill Graham
            Assignee: Bill Graham


If the DemuxManager received more than 5 consecutive errors, it dies with the message "Too many errors, Bail out!".

Let's change to this introduce a configurable number of concurrent exceptions to be encountered before dying. If the value is set to -1, expected behavior is to keep retrying ad infinitum.

Also as part if this bug is to improve logging of how many consecutive errors have occurred, as well as the time they started. A possible future enhancement could be to support an error time threshold as well as an absolute count.

Suggesting the following new config setting. It's a bit verbose, but it's clear.

{noformat}
chukwa.demux.max.error.count.before.shutdown
{noformat}


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.