[
https://issues.apache.org/jira/browse/CHUKWA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421321#comment-13421321
]
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: 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
