Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <13376438.1193347730716.JavaMail.jira@brutus>
Date: Thu, 25 Oct 2007 14:28:50 -0700 (PDT)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1210) Log counters in job history
In-Reply-To: <27353599.1175799032591.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-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-1210:
----------------------------------

    Attachment: job-history-counters-2.patch

I moved the stringifyCounters to Counters.makeCompactString, but there was already a toString method on Counters that does things like put newlines in that I didn't want to disrupt.

> Log counters in job history
> ---------------------------
>
>                 Key: HADOOP-1210
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1210
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Albert Chern
>            Assignee: Owen O'Malley
>            Priority: Minor
>             Fix For: 0.16.0
>
>         Attachments: counters_output, h-1210-job-and-task-status.patch, h-1210-job-and-task-status.patch, h-1210-jobstatus.patch, job-history-counters-2.patch, job-history-counters.patch
>
>
> It would be useful if the value of the global counters were logged to the job history, perhaps even individually for each task after completion.

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