Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 1701 invoked from network); 10 Apr 2010 21:34:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Apr 2010 21:34:30 -0000 Received: (qmail 41465 invoked by uid 500); 10 Apr 2010 21:34:30 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 41075 invoked by uid 500); 10 Apr 2010 21:34:29 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 40883 invoked by uid 99); 10 Apr 2010 21:34:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Apr 2010 21:34:28 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.145.54.173] (HELO mrout3.yahoo.com) (216.145.54.173) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Apr 2010 21:34:22 +0000 Received: from [10.72.168.88] ([10.72.168.88]) by mrout3.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id o3ALWfh6060494; Sat, 10 Apr 2010 14:32:41 -0700 (PDT) Message-ID: <4BC0EE7A.4060901@apache.org> Date: Sat, 10 Apr 2010 14:32:42 -0700 From: Patrick Hunt User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: "zookeeper-dev@hadoop.apache.org" , "zookeeper-user@hadoop.apache.org" , hbase-dev@hadoop.apache.org Subject: 4letter word (monitor) issue in 3.3.0 with nc (netcat) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I discovered a problem using nc with 3.3.0 such as: echo stat | nc localhost 2181 full details here: http://bit.ly/ahkHdb The failure is intermittent for me (timing issue) but I wanted to let everyone know about it given that nc is frequently used for monitoring. Given the nature of the problem you may be seeing results inconsistent with the status of the server (server up but stat not returning data). This does not effect the functioning of the server, just the command itself is impaired. We'll probably do a 3.3.1 relatively soon to correct this (and a few other issues that are slated for 3.3.1). Patrick