You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Ari Rabkin (JIRA)" <ji...@apache.org> on 2009/12/08 21:19:18 UTC

[jira] Commented: (CHUKWA-426) High frequency of adaptor registration and unregistration could prevent existing adaptor to stall

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

Ari Rabkin commented on CHUKWA-426:
-----------------------------------

I don't completely understand this problem. Is this a collector or agent problem? Can you explain in a bit more detail?

> High frequency of adaptor registration and unregistration could prevent existing adaptor to stall
> -------------------------------------------------------------------------------------------------
>
>                 Key: CHUKWA-426
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-426
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>            Priority: Minor
>
> The existing adaptor might not retrieve data because agent was designed to loop through the adaptors to send the information.  When the frequency of registering and unregistering is more frequent than chunk writer, like many tasks attempting to stream their metrics over, the existing adaptors do not get loops.  The easy workaround is to have socket appender ready, and we don't need to worry about this issue.  However, this is still an general issue, if the chunk writer write time is longer than registration interval with high registration frequencies.

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