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 7283A104AB for ; Tue, 4 Feb 2014 22:32:33 +0000 (UTC) Received: (qmail 79746 invoked by uid 500); 4 Feb 2014 22:32:13 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 79619 invoked by uid 500); 4 Feb 2014 22:32:11 -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 79570 invoked by uid 99); 4 Feb 2014 22:32:11 -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 22:32:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of comomore@gmail.com designates 209.85.220.170 as permitted sender) Received: from [209.85.220.170] (HELO mail-vc0-f170.google.com) (209.85.220.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 22:32:07 +0000 Received: by mail-vc0-f170.google.com with SMTP id hu8so6348694vcb.15 for ; Tue, 04 Feb 2014 14:31:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=SDi4krtCM8x4rZ90tQ76+ERaCUuget180Yk9II4CG3A=; b=Y2fVH+gv6l66jcu2q6zXOtKrzAJoYsS329s/KUFsy6ZPPQwpg+nPBKt/TxIPrHR/Bd /iTT/MQs6JqK4p0xedMGVY4cwPzeclKV5xrsHmaLy5IKpImb4LXIRyZuEYMm83QZ95jR soi2+FICEDRFedKkthx3rUl4pdoRcyQLO37HT3gf8LYS0bFyZNqth9M4L0SLveIol/PY RiG+mboD78/gFjECalrbc6czk6xy1xrOKu5GFY3d5i33qQ+yYe5kLMVoNORur5td5JZZ PROJUrnuy7QHQj1V9QQPXHqNMqcTkOf/DSzJ6yIOr1ueieZ/a8iHgaDeXUF5Omye5M8C f/ww== MIME-Version: 1.0 X-Received: by 10.220.191.134 with SMTP id dm6mr35183431vcb.16.1391553106599; Tue, 04 Feb 2014 14:31:46 -0800 (PST) Received: by 10.221.4.131 with HTTP; Tue, 4 Feb 2014 14:31:46 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Feb 2014 16:31:46 -0600 Message-ID: Subject: Re: Question 1: JMX binding, Question 2: Logging From: srmore To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e0158a82a9ae6a004f19c3454 X-Virus-Checked: Checked by ClamAV on apache.org --089e0158a82a9ae6a004f19c3454 Content-Type: text/plain; charset=ISO-8859-1 Hello Kyle, For your first question, you need to create aliases to localhost e.g. 127.0.0.2,127.0.0.3 etc. this should get you going. About the logging issue, I think if your instance failing before it gets to long anything, as an example you can strart one instance and make sure it logs correctly. Hope that helps. Sandeep On Tue, Feb 4, 2014 at 4:25 PM, Kyle Crumpton (kcrumpto) wrote: > Hi all, > > I'm fairly new to Cassandra. I'm deploying it to a PaaS. One thing this > entails is that it must be able to have more than one instance on a single > node. I'm running into the problem that JMX binds to 0.0.0.0:7199. My > question is this: Is there a way to configure this? I have actually found > the post that said to change the the following > > JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=127.1.246.3" where > 127.1.246.3 is the IP I want to bind to.. > > This actually did not change the JMX binding by any means for me. I saw a > post about a "jmx listen address" in cassandra.yaml and this also did not > work. > Any clarity on whether this is bindable at all? Or if there are plans for > it? > > Also- > > I have logging turned on. For some reason, though, my Cassandra is not > actually logging as intended. My log folder is actually empty after each > (failed) run (due to the port being taken by my other cassandra process). > > Here is an actual copy of my log4j-server.properites file: > http://fpaste.org/74470/15510941/ > > Any idea why this might not be logging? > > Thank you and best regards > > Kyle > --089e0158a82a9ae6a004f19c3454 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Kyle,
For your first qu= estion, you need to create aliases to localhost e.g. 127.0.0.2,127.0.0.3 et= c. this should get you going.
About the logging issue, I think if = your instance failing before it gets to long anything, as an example you ca= n strart one instance and make sure it logs correctly.

Hope that helps.
Sandeep




On Tue, Feb 4, 2014 at 4:25 PM, Kyle Crumpton (kcrumpto) <kcrumpto@= cisco.com> wrote:
Hi all,

I'm fairly new to Cassandra. I'm deploying it to a PaaS. One t= hing this entails is that it must be able to have more than one instance on= a single node. I'm running into the problem that JMX binds to 0.0.0.0:7199. My question is= this: Is there a way to configure this? I have actually found the post that said to change the the= following=A0
JVM_O= PTS=3D"$JVM_OPTS -Djava.rmi.server.hostname=3D127.1.246.3" where = 127.1.246.3 is the IP I want to bind to..=A0
This actually did not change the JMX binding by any means for me. I sa= w a post about a "jmx listen address" in cassandra.yaml and this = also did not work.=A0
Any clarity on whether this is bindable at all? Or if there are plans = for it?

Also-

I have logging turned on. For some reason, though, my Cassandra is not= actually logging as intended. My log folder is actually empty after each (= failed) run (due to the port being taken by my other cassandra process).

Here is an actual copy of my log4j-server.properites file:=A0http://fpaste.org/7= 4470/15510941/

Any idea why this might not be logging?

Thank you and best regards

Kyle=A0

--089e0158a82a9ae6a004f19c3454--