[
https://issues.apache.org/jira/browse/CHUKWA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426289#comment-13426289
]
Hudson commented on CHUKWA-650:
-------------------------------
Integrated in Chukwa-trunk #455 (See
[https://builds.apache.org/job/Chukwa-trunk/455/])
CHUKWA-650. Re-configure Demux ReduceNumber without re-starting the
DemuxManager service. Contributed by Jie Huang (Revision 1367839)
Result = FAILURE
asrabkin :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1367839
Files :
* /incubator/chukwa/trunk/CHANGES.txt
*
/incubator/chukwa/trunk/src/main/java/org/apache/hadoop/chukwa/extraction/demux/DemuxManager.java
> 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
