Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <1900767101.1239151212927.JavaMail.jira@brutus>
Date: Tue, 7 Apr 2009 17:40:12 -0700 (PDT)
From: "Mac Yang (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Updated: (CHUKWA-68) Race condition could stop log file
 streaming
In-Reply-To: <1382311804.1238463590459.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-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mac Yang updated CHUKWA-68:
---------------------------

    Priority: Major  (was: Blocker)

Removing this from the blocker list since this can't be easily reproduced and code review does not show any obvious issue.


> Race condition could stop log file streaming
> --------------------------------------------
>
>                 Key: CHUKWA-68
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-68
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection
>         Environment: Redhat 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>
> When log file is actively writing with log4j appender, and fileTailingAdaptor is behind.  There is a possibility that restart the java program might stop log file streaming.
> Here is an example of what could go wrong:
> 04:01 Shutdown Name Node.
> 04:01 Terminator Thread kick in and streaming the remaining log.
> 04:02 Name Node Started up
> 04:03 Register of namenode log file failed because it is already streaming.
> 04:20 Terminator Thread finished the log file, unregister name node log for streaming.

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