chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Huang (JIRA)" <>
Subject [jira] [Commented] (CHUKWA-650) Re-configure Demux ReduceNumber without re-starting the DemuxManager service
Date Tue, 24 Jul 2012 10:48:34 GMT


Jie Huang commented on CHUKWA-650:

Sorry, I missed one line to reload the configuration before reading that item. Here attaches
the updated solution. I will verify it by running over the real cluster ASAP.
Besides, instead of reloading the existing conf object, we'd better to copy a new configuration
instance before reloading, and pass this new instance to Demux. It not only makes the reduce
number updated, but also reloads other necessary items as well for Demux process.  

Any idea about this proposal?  Thanks
> Re-configure Demux ReduceNumber without re-starting the DemuxManager service
> ----------------------------------------------------------------------------
>                 Key: CHUKWA-650
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message