You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2008/11/21 23:37:44 UTC
[jira] Created: (HADOOP-4711) Chukwa - Add a config parameter to
allow agent to talk to the same collector until connection fails.
Chukwa - Add a config parameter to allow agent to talk to the same collector until connection fails.
----------------------------------------------------------------------------------------------------
Key: HADOOP-4711
URL: https://issues.apache.org/jira/browse/HADOOP-4711
Project: Hadoop Core
Issue Type: New Feature
Environment: Redhat EL 4.5, Java 1.6, Hadoop trunk
Reporter: Eric Yang
In chukwa agent, we added ability to rotate collector on each HTTP post. RAD Lab is using Chukwa Agent differently, and would like to have the option to keep agent on the same collector. On the smaller scale of the Chukwa, it makes sense to process data without the map reduce job. A new interface needs to be created as a T pipe line to stream data from collector directly into a Database or external storage. In this configuration, it is better to channel similar data to the same collector to reduce the cost of reassembling chunks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-4711) Chukwa - Add a config parameter to
allow agent to talk to the same collector until connection fails.
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang resolved HADOOP-4711.
-------------------------------
Resolution: Fixed
Assignee: Eric Yang
Since we removed black list feature, Chukwa Agent will stay on the same collector until the collect fail to respond. Hence, this ticket is resolved by HADOOP-4805.
> Chukwa - Add a config parameter to allow agent to talk to the same collector until connection fails.
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4711
> URL: https://issues.apache.org/jira/browse/HADOOP-4711
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/chukwa
> Environment: Redhat EL 4.5, Java 1.6, Hadoop trunk
> Reporter: Eric Yang
> Assignee: Eric Yang
>
> In chukwa agent, we added ability to rotate collector on each HTTP post. RAD Lab is using Chukwa Agent differently, and would like to have the option to keep agent on the same collector. On the smaller scale of the Chukwa, it makes sense to process data without the map reduce job. A new interface needs to be created as a T pipe line to stream data from collector directly into a Database or external storage. In this configuration, it is better to channel similar data to the same collector to reduce the cost of reassembling chunks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4711) Chukwa - Add a config parameter to
allow agent to talk to the same collector until connection fails.
Posted by "Mac Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mac Yang updated HADOOP-4711:
-----------------------------
Component/s: contrib/chukwa
> Chukwa - Add a config parameter to allow agent to talk to the same collector until connection fails.
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4711
> URL: https://issues.apache.org/jira/browse/HADOOP-4711
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/chukwa
> Environment: Redhat EL 4.5, Java 1.6, Hadoop trunk
> Reporter: Eric Yang
>
> In chukwa agent, we added ability to rotate collector on each HTTP post. RAD Lab is using Chukwa Agent differently, and would like to have the option to keep agent on the same collector. On the smaller scale of the Chukwa, it makes sense to process data without the map reduce job. A new interface needs to be created as a T pipe line to stream data from collector directly into a Database or external storage. In this configuration, it is better to channel similar data to the same collector to reduce the cost of reassembling chunks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.