Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <1573177096.1238628913205.JavaMail.jira@brutus>
Date: Wed, 1 Apr 2009 16:35:13 -0700 (PDT)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Updated: (CHUKWA-75) iostat output overflow
In-Reply-To: <1253741828.1238552210590.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-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated CHUKWA-75:
----------------------------

    Attachment: CHUKWA-75-2.patch

Bump up the number to 1+e12, and skip the key/value pair, if it was a overflow.  In today's disk, the highest throughput is ~100MB/second.  It's unlike any number should reach 1+e12 in iostat.  By skipping the key/value pair, we eliminate null pointer exception problem for the down stream application.

> iostat output overflow
> ----------------------
>
>                 Key: CHUKWA-75
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-75
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: Data Processors
>         Environment: Redhat 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: CHUKWA-75-2.patch, CHUKWA-75.patch
>
>
> On older systems, iostat metrics contain random overflow.  The plan is the put in a filter to remove the overflow in the demux parser to improve the data quality.

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