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 2012/08/01 03:40:39 UTC

[jira] [Resolved] (CHUKWA-650) Re-configure Demux ReduceNumber without re-starting the DemuxManager service

     [ https://issues.apache.org/jira/browse/CHUKWA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ari Rabkin resolved CHUKWA-650.
-------------------------------

    Resolution: Fixed

I just committed this. Thanks. :)
                
> Re-configure Demux ReduceNumber without re-starting the DemuxManager service
> ----------------------------------------------------------------------------
>
>                 Key: CHUKWA-650
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-650
>             Project: Chukwa
>          Issue Type: Improvement
>          Components: Data Processors
>    Affects Versions: 0.6.0
>            Reporter: Jie Huang
>            Assignee: Jie Huang
>         Attachments: chukwa-650.patch
>
>
> Currently, DemuxManager controls the Demux's reduce number by reading "CHUKWA_DEMUX_REDUCER_COUNT_FIELD" at the initialization part. It is impossible to tune that reduce number before the next round of demux happens. The only way is to restart that DemuxManager service. I wonder if it is OK to parse that configuration item in  runDemux() function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira