chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mac Yang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-75) iostat output overflow
Date Wed, 01 Apr 2009 22:18:12 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694790#action_12694790
] 

Mac Yang commented on CHUKWA-75:
--------------------------------

Is there an expectation that this record type will never contain null value? Given the wide
range of input sources and the plugable nature of the system, seems to me the generic components
like the demux pipeline and the DumpRecord tool should check for null value irregardless of
what we decide to do here.

If we use some other value instead of null then all the down stream components will need to
check for that, in addition to checking for null. Besides, that value will need to be reserved
to signify missing data point, and needs to be followed cross data sources. 

> 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-1.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.


Mime
View raw message