Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <2085195227.1245432247424.JavaMail.jira@brutus>
Date: Fri, 19 Jun 2009 10:24:07 -0700 (PDT)
From: "Jerome Boulon (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Resolved: (CHUKWA-303) collector gets stuck when unable to
 write to hdfs
In-Reply-To: <329243224.1245258847334.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jerome Boulon resolved CHUKWA-303.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.3.0

Fixed by CHUKWA-313

> collector gets stuck when unable to write to hdfs
> -------------------------------------------------
>
>                 Key: CHUKWA-303
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-303
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection
>    Affects Versions: 0.2.0
>            Reporter: Eric Yang
>            Assignee: Jerome Boulon
>            Priority: Blocker
>             Fix For: 0.2.0, 0.3.0
>
>
> The recent change to collector may have problems.  Last night, I shutdown hdfs, and expecting the collectors to bail out by themselves, and restart by the watchdog.  However, this morning, the collector was still running and sending 0 bytes to the system.  Port 4080 isn't accepting any more HTTP post.  This indicates that the jettyCollector may have been shutdown but the java program didn't exist.  The only change to collector is the LocalWriter enhancement, and it isn't enabled.

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