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 9B09ADDB9 for ; Wed, 29 Aug 2012 06:42:07 +0000 (UTC) Received: (qmail 91187 invoked by uid 500); 29 Aug 2012 06:42:05 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 91087 invoked by uid 500); 29 Aug 2012 06:42:04 -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 91040 invoked by uid 99); 29 Aug 2012 06:42:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2012 06:42:02 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jcistaro@netflix.com designates 69.53.237.162 as permitted sender) Received: from [69.53.237.162] (HELO exout103.netflix.com) (69.53.237.162) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2012 06:41:58 +0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=s1024;d=netflix.com; h=from:to:subject:date:message-id:in-reply-to:content-type:mime-version; bh=EcCxilN1VkRgGV+TX2uV2BvdD30=; b=OtdtnsprZAmSeIKYtHBLKni68jIFz1N8FhaXIyLf3v/Eo3MvY3m8jkJ35tFpSFVvil0JWKiK 8w+putswd7DFOZFlK9fuEEygff8+U1eIUDpn6w1ezw/QoGd3oiAxwFO5wYeIiMzTQkQA3/BX S/ls33YiUZcmnKlW6tc587aclf8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;d=netflix.com; h=from:to:subject:date:message-id:in-reply-to:content-type:mime-version; b=MxNbhpztuBXcM/Aj/Zm9XRukKtEO4cigaaajok0Hbj+jl0enrCJD+ifcw9nRjHRmUocvbsOy ICrEU4U+snhXI2ec2vPbpdiVVPcI9RRuTcoPiq7SyPRExipqArxdksBTXNGAFqStQjhtP4Eb zuoETXpVR8PzLu8W3s5rjtDv+I8= Received: from EXFE101.corp.netflix.com (10.64.32.161) by exout103.netflix.com (10.64.240.73) with Microsoft SMTP Server (TLS) id 14.2.298.4; Tue, 28 Aug 2012 23:41:37 -0700 Received: from EXMB102.corp.netflix.com ([169.254.2.85]) by exfe101.corp.netflix.com ([10.64.32.161]) with mapi id 14.02.0283.003; Tue, 28 Aug 2012 23:41:37 -0700 From: Jim Cistaro To: "user@cassandra.apache.org" Subject: Re: JMX(RMI) dynamic port allocation problem still exists? Thread-Topic: JMX(RMI) dynamic port allocation problem still exists? Thread-Index: AQHNhJ01rUm6BBeuf0qRDrpC55FGvZduq9UAgAABGoCAAGNSAIAAtg4AgACTHwA= Date: Wed, 29 Aug 2012 06:41:36 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.10.0.110310 x-originating-ip: [10.64.24.14] Content-Type: multipart/alternative; boundary="_000_CC6306A71600Ajcistaronetflixcom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CC6306A71600Ajcistaronetflixcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You may already be aware, but another possible solution is to use MX4J to d= o your JMX over REST (I have not tried this myself yet). http://wiki.apache.org/cassandra/Operations#Monitoring_with_MX4J From: Yang > Reply-To: > Date: Tue, 28 Aug 2012 07:55:00 -0700 To: > Subject: Re: JMX(RMI) dynamic port allocation problem still exists? Thanks Nick. it would be nice to pack such work-arounds together with Cassandra, and ena= ble it with a command line arg in the start up script, so that the end-use= r has a more smooth usage experience ----- we did spend some time before to debug the po= rts issues, and find a trick for that. I imagine a lot of users will have to go through the same process since "cl= osing all ports" is the default EC2 network security policy for most compan= ies. Or at least add a link for the fix in the installation wikis such as h= ttp://www.datastax.com/docs/1.1/install/install_ami Yang On Mon, Aug 27, 2012 at 9:03 PM, Nick Bailey > wrote: The problem still exists. There was a discussion about resolving inside cassandra here: https://issues.apache.org/jira/browse/CASSANDRA-2967 But the ultimate resolution was that since workarounds like the one you mentioned exist it would be left as is for now. On Mon, Aug 27, 2012 at 6:07 PM, Yang > wrote: > no, the priblem is that jmx listens on 7199, once an incoming connection = is > made, it literally tells the other side "come and connect to me on these = 2 > rmi ports", and open up 2 random Rmi ports > > we used to use the trick in the above link to resolve this > > On Aug 27, 2012 3:04 PM, "Hiller, Dean" > wrote: >> >> In cassandra-env.sh, search on JMX_PORT and it is set to 7199 (ie. Fixed= ) >> so that solves your issue, correct? >> >> Dean >> >> From: Yang >> >> Reply-To: "user@cassandra.apache.org>" >> >> >> Date: Monday, August 27, 2012 3:44 PM >> To: "user@cassandra.apache.org>" >> >> >> Subject: JMX(RMI) dynamic port allocation problem still exists? >> >> ow, does Cassandra come with an out-of-the box solution to fix the above >> problem? or do I have >> to create that little javaagent jar myself? --_000_CC6306A71600Ajcistaronetflixcom_ Content-Type: text/html; charset="us-ascii" Content-ID: <76B5E939EB3F934CB86A3E82EB7C489F@netflix.com> Content-Transfer-Encoding: quoted-printable
You may already be aware, but another possible solution is to use MX4J= to do your JMX over REST (I have not tried this myself yet).


From: Yang <teddyyyy123@gmail.com>
Reply-To: <user@cassandra.apache.org>
Date: Tue, 28 Aug 2012 07:55:00 -07= 00
To: <user@cassandra.apache.org>
Subject: Re: JMX(RMI) dynamic port = allocation problem still exists?

Thanks Nick.

it would be nice to pack such work-arounds together with Cassandra, an= d enable it with a command line arg in the start up script,  so that t= he end-user has a more
smooth usage experience ----- we did spend some time before to debug t= he ports issues, and find a trick for that.
I imagine a lot of users will have to go through the same process sinc= e "closing all ports" is the default EC2 network security policy = for most companies. Or at least add a link for the fix in the installation = wikis such as http://= www.datastax.com/docs/1.1/install/install_ami



Yang

On Mon, Aug 27, 2012 at 9:03 PM, Nick Bailey <nick@datastax.co= m> wrote:
The problem still exists. There was a discussion about resolving
inside cassandra here:

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

But the ultimate resolution was that since workarounds like the one
you mentioned exist it would be left as is for now.

On Mon, Aug 27, 2012 at 6:07 PM, Yang <teddyyyy123@gmail.com> wrote:
> no, the priblem is that jmx listens on 7199, once an incoming connecti= on is
> made, it literally tells the other side "come and connect to me o= n these 2
> rmi ports",  and open up  2 random  Rmi ports
>
> we used to use the trick in the above link to resolve this
>
> On Aug 27, 2012 3:04 PM, "Hiller, Dean" <Dean.Hiller@nrel.gov> wrote:
>>
>> In cassandra-env.sh, search on JMX_PORT and it is set to 7199 (ie.= Fixed)
>> so that solves your issue, correct?
>>
>> Dean
>>
>> From: Yang <teddyyyy12= 3@gmail.com<mailto:teddyyyy= 123@gmail.com>>
>> Reply-To: "user@= cassandra.apache.org<mailto:user@cassandra.apache.org>"
>> <user@cassandra.ap= ache.org<mailto:user@ca= ssandra.apache.org>>
>> Date: Monday, August 27, 2012 3:44 PM
>> To: "user@cassan= dra.apache.org<mailto:u= ser@cassandra.apache.org>"
>> <user@cassandra.ap= ache.org<mailto:user@ca= ssandra.apache.org>>
>> Subject: JMX(RMI) dynamic port allocation problem still exists? >>
>> ow, does Cassandra come with an out-of-the box solution to fix the= above
>> problem? or do I have
>> to create that little javaagent jar myself?

 --_000_CC6306A71600Ajcistaronetflixcom_--