[
https://issues.apache.org/jira/browse/CHUKWA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787774#action_12787774
]
Eric Yang commented on CHUKWA-426:
----------------------------------
I suspected it was stuck in
org.apache.hadoop.chukwa.datacollection.adaptor.filetailer.FileTailer run
method. Line 90 to 93. I am not sure if that was possible. If not possible,
maybe invalidate this bug. However, my system recovered after I shutdown the
excessive adaptor registrations.
> 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.
