Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2070096639.1224069944517.JavaMail.jira@brutus>
Date: Wed, 15 Oct 2008 04:25:44 -0700 (PDT)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4413) Capacity Scheduler to provide a
 scheduler history log to record actions taken and why
In-Reply-To: <1055775954.1224034604168.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639816#action_12639816 ] 

Vinod K V commented on HADOOP-4413:
-----------------------------------

All the scheduler log goes to the same log as JobTracker now. May be we should move the scheduler logging to a new log file. I already see that scheduler logging statements and JT logging statements get drowned in each other. And in debug level, the situation only gets worse. But one big advantage we can have by a single log file is the time-line of various events occurring in a scheduler w.r.t events happening in the JT.

> Capacity Scheduler to provide a scheduler history log to record actions taken and why
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4413
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4413
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/capacity-sched
>            Reporter: Mac Yang
>
> It would be very useful if the capacity scheduler can provide a log that record the decisions made and actions taken by the scheduler.

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