Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2560A9343 for ; Mon, 26 Mar 2012 19:55:29 +0000 (UTC) Received: (qmail 46472 invoked by uid 500); 26 Mar 2012 19:55:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 46448 invoked by uid 500); 26 Mar 2012 19:55:26 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 46388 invoked by uid 99); 26 Mar 2012 19:55:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 19:55:24 +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 yiming.sun@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 19:55:19 +0000 Received: by werb10 with SMTP id b10so5337480wer.31 for ; Mon, 26 Mar 2012 12:54:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=IBasOo4stslv/azoD9anS2KwwgEERlZkCKPlDwXo6Dw=; b=dsTRzpfKwca8NcIpb95SninoCQB2TMZRN2W28SPJtVuBrLr3QbXkP2+vkjq5FERcYj KGHzA4XJ+NwalJYGU20XzxxapGqLcmLS89PU+urZQ9cfakuaafHiK0cuxxZFLZlXInh3 A6Nt6WSw7RZU1d17xM61axVTOOoTkJL3GZFatPtkZKcuE33240EVUyuoFb16AzSPSR6G s6j1RKbF1agGObQF2VOq0eHlqYib1Y0FYaCeTyPWyy5gQ5Xggyf2RMXSlWqXMqE4GgEZ aFO+OfSecpGNO4KIhKNZYCHKvJHm4hdyW72dum22AzSMGLqJ2Rs3S1XF/QHZC1vbNIhg mITw== Received: by 10.180.101.72 with SMTP id fe8mr21344436wib.4.1332791698646; Mon, 26 Mar 2012 12:54:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.17.207 with HTTP; Mon, 26 Mar 2012 12:54:38 -0700 (PDT) In-Reply-To: References: From: Yiming Sun Date: Mon, 26 Mar 2012 15:54:38 -0400 Message-ID: Subject: Re: what other ports than 7199 need to be open for nodetool to work? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d04430662c1e7c604bc2abf07 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04430662c1e7c604bc2abf07 Content-Type: text/plain; charset=ISO-8859-1 Thanks Nick -- I didn't know about this ticket. Good to know. Yes, nodetool doesn't do anything special - but I still wish I could use nodetool to examine other nodes, instead of having to ssh to other nodes first and then nodetool each one (i am lazy :-). -- Y. On Mon, Mar 26, 2012 at 3:50 PM, Nick Bailey wrote: > You are correct about the second random dynamic port. There is a > ticket open to fix that as well as some other jmx issues: > > https://issues.apache.org/jira/browse/CASSANDRA-2967 > > Regarding nodetool, it doesn't do anything special. Nodetool is often > used to connect to 'localhost' which generally does not have any > firewall rules at all so it usually works. It is still connecting to a > random second port though. > > On Mon, Mar 26, 2012 at 2:42 PM, Yiming Sun wrote: > > Hi, > > > > We opened port 7199 on a cassandra node, but were unable to get a > nodetool > > to talk to it remotely unless we turn off the firewall entirely. So what > > other ports should be opened for this -- online posts all indicate that > JMX > > uses a random dynamic port, which would be difficult to create a firewall > > exception unless writing a custom java agent. So we just wondering if > > cassandra nodetool uses a specific port/port range. Thanks. > > > > -- Y. > --f46d04430662c1e7c604bc2abf07 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Nick -- I didn't know about this ticket. =A0Good to know.
Yes, nodetool doesn't do anything special - but I still wi= sh I could use nodetool to examine other nodes, instead of having to ssh to= other nodes first and then nodetool each one (i am lazy :-).

-- Y.

On Mon, Mar 26,= 2012 at 3:50 PM, Nick Bailey <nick@datastax.com> wrote:
You are correct about the second random dynamic port. There is a
ticket open to fix that as well as some other jmx issues:

https://issues.apache.org/jira/browse/CASSANDRA-2967

Regarding nodetool, it doesn't do anything special. Nodetool is often used to connect to 'localhost' which generally does not have any firewall rules at all so it usually works. It is still connecting to a
random second port though.

On Mon, Mar 26, 2012 at 2:42 PM, Yiming Sun <yiming.sun@gmail.com> wrote:
> Hi,
>
> We opened port 7199 on a cassandra node, but were unable to get a node= tool
> to talk to it remotely unless we turn off the firewall entirely. =A0So= what
> other ports should be opened for this -- online posts all indicate tha= t JMX
> uses a random dynamic port, which would be difficult to create a firew= all
> exception unless writing a custom java agent. =A0So we just wondering = if
> cassandra nodetool uses a specific port/port range. =A0Thanks.
>
> -- Y.

--f46d04430662c1e7c604bc2abf07--