Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 15207106A3 for ; Tue, 4 Feb 2014 00:30:50 +0000 (UTC) Received: (qmail 55466 invoked by uid 500); 4 Feb 2014 00:30:49 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 55403 invoked by uid 500); 4 Feb 2014 00:30:49 -0000 Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.incubator.apache.org Delivered-To: mailing list user@storm.incubator.apache.org Received: (qmail 55394 invoked by uid 99); 4 Feb 2014 00:30:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 00:30:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of uzunbaz@gmail.com designates 209.85.216.53 as permitted sender) Received: from [209.85.216.53] (HELO mail-qa0-f53.google.com) (209.85.216.53) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 00:30:43 +0000 Received: by mail-qa0-f53.google.com with SMTP id cm18so11313677qab.12 for ; Mon, 03 Feb 2014 16:30:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=sEVyZJ5NTD60FUSIY1/DP3qv90Jh9jhH6OsshzeGuZI=; b=cLMWi46a3NuE9kopJBJOqCJrt3ZeYc0Bl3UiQ+KJjv2fjUf+zhlkFOVMuIH4vflvkR 7kYoDStni7u0jA8Iujpacp8+2eCSSMOJPlXAyLfqDvHfZCEH0W8geELRYBwrHkRgc6nA hQWrVdwH7LvVMSESUfneAcTDVxBCJLvtee3TQwC3c9N3MKohfWI3DHyyxV8oZsHQ8ORR MSjoT54NL/FvaVJC1geBCtOwRA6O5qpWdyoHVhW9zNpXegayeviXjulr6gKGggm/F+E8 5JI0LcqrjpM4Xq/NgLj1p/boI8TB/p8FKRLmrse476LuA4KSqqnAKFkr9F6sxzXc1RS8 PqpQ== MIME-Version: 1.0 X-Received: by 10.224.74.129 with SMTP id u1mr60580444qaj.49.1391473822591; Mon, 03 Feb 2014 16:30:22 -0800 (PST) Received: by 10.224.182.132 with HTTP; Mon, 3 Feb 2014 16:30:22 -0800 (PST) Date: Mon, 3 Feb 2014 16:30:22 -0800 Message-ID: Subject: About Netty message buffers and monitoring them From: Serkan Uzunbaz To: user@storm.incubator.apache.org Content-Type: multipart/alternative; boundary=089e01538ddce8f15a04f189be75 X-Virus-Checked: Checked by ClamAV on apache.org --089e01538ddce8f15a04f189be75 Content-Type: text/plain; charset=ISO-8859-1 Hi all, I am using the Netty as the transport layer in Storm and have a few questions: 1. My understanding is that there are two netty message queue per worker process (one receive queue and one send queue per worker) and the buffer_size configuration (storm.messaging.netty.buffer_size) controls the size of the both. Is that right? 2. I can monitor the population of the internal message queues using a metrics consumer. Is there a way to monitor the population of the netty message queues? Thanks, -Serkan --089e01538ddce8f15a04f189be75 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
I am using the Netty = as the transport layer in Storm and have a few questions:
1. My understanding is that there are two netty message queue p= er worker process (one receive queue and one send queue per worker) and the= buffer_size configuration (storm.messaging.netty.buffer_size) controls the= size of the both. Is that right?
2. I can monitor the population of the internal message queues using = a metrics consumer. Is there a way to monitor the population of the netty m= essage queues?

Thanks,
-Serkan
--089e01538ddce8f15a04f189be75--