Return-Path: X-Original-To: apmail-incubator-chukwa-dev-archive@www.apache.org Delivered-To: apmail-incubator-chukwa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 13AB3957A for ; Tue, 24 Jul 2012 00:30:36 +0000 (UTC) Received: (qmail 24234 invoked by uid 500); 24 Jul 2012 00:30:35 -0000 Delivered-To: apmail-incubator-chukwa-dev-archive@incubator.apache.org Received: (qmail 23651 invoked by uid 500); 24 Jul 2012 00:30:35 -0000 Mailing-List: contact chukwa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: chukwa-dev@incubator.apache.org Delivered-To: mailing list chukwa-dev@incubator.apache.org Received: (qmail 23621 invoked by uid 99); 24 Jul 2012 00:30:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2012 00:30:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AE529142823 for ; Tue, 24 Jul 2012 00:30:34 +0000 (UTC) Date: Tue, 24 Jul 2012 00:30:34 +0000 (UTC) From: "Ari Rabkin (JIRA)" To: chukwa-dev@incubator.apache.org Message-ID: <117346962.93604.1343089834715.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1828269751.89565.1343013697477.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (CHUKWA-650) Re-configure Demux ReduceNumber without re-starting the DemuxManager service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CHUKWA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421056#comment-13421056 ] Ari Rabkin commented on CHUKWA-650: ----------------------------------- Hrm. Does config get re-loaded without restarting demux? If you tell me you have deployed this and it works, I'll commit it. > 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