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 2010/04/13 21:10:50 UTC
[jira] Created: (CHUKWA-476) Scaling the real-time channel
Scaling the real-time channel
-----------------------------
Key: CHUKWA-476
URL: https://issues.apache.org/jira/browse/CHUKWA-476
Project: Hadoop Chukwa
Issue Type: Improvement
Components: data collection
Reporter: Ari Rabkin
Right now, the real-time channel does the right thing for the one-collector case, but is awkward to use in the multi-collector case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CHUKWA-476) Scaling the real-time channel
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856558#action_12856558 ]
Ari Rabkin commented on CHUKWA-476:
-----------------------------------
I envision a Java class or small library that takes a list of collectors and a filter pattern, and then hands back anything matching that pattern from any collector.
This means that clients will get a unified view of what's happening across the cluster.
> Scaling the real-time channel
> -----------------------------
>
> Key: CHUKWA-476
> URL: https://issues.apache.org/jira/browse/CHUKWA-476
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: data collection
> Reporter: Ari Rabkin
>
> Right now, the real-time channel does the right thing for the one-collector case, but is awkward to use in the multi-collector case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CHUKWA-476) Scaling the real-time channel
Posted by "Jerome Boulon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856577#action_12856577 ]
Jerome Boulon commented on CHUKWA-476:
--------------------------------------
This utility class could be used in a specific writer to send a fraction of the incoming traffic to a remote application. The remote application being the Client app that Ari refer to.
Useful filtering will be on:
- DataType
- HostName
- "Application/Stream"'s name
Do we want to work at the Chunk level only or do we want to open it? Aka do we want to work only on the metadata or everything?
> Scaling the real-time channel
> -----------------------------
>
> Key: CHUKWA-476
> URL: https://issues.apache.org/jira/browse/CHUKWA-476
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: data collection
> Reporter: Ari Rabkin
>
> Right now, the real-time channel does the right thing for the one-collector case, but is awkward to use in the multi-collector case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira