From user-return-35651-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Jul 30 15:47:27 2013 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 3745010772 for ; Tue, 30 Jul 2013 15:47:27 +0000 (UTC) Received: (qmail 86117 invoked by uid 500); 30 Jul 2013 15:47:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 86107 invoked by uid 500); 30 Jul 2013 15:47:24 -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 86096 invoked by uid 99); 30 Jul 2013 15:47:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2013 15:47:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=9166a5551=Ben_Boule@rapid7.com designates 208.118.227.12 as permitted sender) Received: from [208.118.227.12] (HELO smtp002.rapid7.com) (208.118.227.12) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2013 15:47:19 +0000 Received-SPF: None (smtp002.rapid7.com: no sender authenticity information available from domain of Ben_Boule@rapid7.com) identity=mailfrom; client-ip=10.3.20.111; receiver=smtp002.rapid7.com; envelope-from="Ben_Boule@rapid7.com"; x-sender="Ben_Boule@rapid7.com"; x-conformance=spf_only Received-SPF: None (smtp002.rapid7.com: no sender authenticity information available from domain of postmaster@BOSTONEX.tor.rapid7.com) identity=helo; client-ip=10.3.20.111; receiver=smtp002.rapid7.com; envelope-from="Ben_Boule@rapid7.com"; x-sender="postmaster@BOSTONEX.tor.rapid7.com"; x-conformance=spf_only X-IronPort-AV: E=Sophos;i="4.89,778,1367985600"; d="scan'208,217";a="10518503" Received: from unknown (HELO BOSTONEX.tor.rapid7.com) ([10.3.20.111]) by smtp002.rapid7.com with ESMTP/TLS/AES128-SHA; 30 Jul 2013 11:46:58 -0400 Received: from BOSTONEX.tor.rapid7.com ([::1]) by BOSTONEX.tor.rapid7.com ([::1]) with mapi id 14.01.0270.001; Tue, 30 Jul 2013 11:46:58 -0400 From: Ben Boule To: "user@cassandra.apache.org" Subject: RE: Determining Snitch at Runtime Thread-Topic: Determining Snitch at Runtime Thread-Index: Ac6NOu21ruHc5xo5SfyWuUhOOcDnXQAAQVFB Date: Tue, 30 Jul 2013 15:46:57 +0000 Message-ID: <72199978CE4FB345A2A454C6FEAAB425186D0CA3@BOSTONEX.tor.rapid7.com> References: <72199978CE4FB345A2A454C6FEAAB425186CEC95@BOSTONEX.tor.rapid7.com> In-Reply-To: <72199978CE4FB345A2A454C6FEAAB425186CEC95@BOSTONEX.tor.rapid7.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.100.68] Content-Type: multipart/alternative; boundary="_000_72199978CE4FB345A2A454C6FEAAB425186D0CA3BOSTONEXtorrapi_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_72199978CE4FB345A2A454C6FEAAB425186D0CA3BOSTONEXtorrapi_ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable It looks like I can infer this from the local table in the system schema by= looking at the datacenter value. Would this be a bad bad thing to do? Thanks, Ben ________________________________ From: Ben Boule [Ben_Boule@rapid7.com] Sent: Tuesday, July 30, 2013 11:41 AM To: user@cassandra.apache.org Subject: Determining Snitch at Runtime Hi Everyone, Sorry if the answer to this question is out there, I can't seem to find it = by searching. Is there a way to read the endpoint_snitch at runtime, preferably from a CQ= L query, but fine if it's available through an older API? (Or JMX?) We're automating creating clusters & provisioning our schema appropriately = into them, it'd be great if the provisioning program could figure this out = once it connected to the cluster before creating keyspaces. Right now we a= re having to track a maze of parameters to make sure that the cluster gets = created with the right snitch, and then that we can pass a parameter into t= he provisioning program to tell it which topology strategy to use. Thank you, Ben This electronic message contains information which may be confidential or p= rivileged. The information is intended for the use of the individual or ent= ity named above. If you are not the intended recipient, be aware that any d= isclosure, copying, distribution or use of the contents of this information= is prohibited. If you have received this electronic transmission in error,= please notify us by e-mail at (postmaster@rapid7.com) immediately. This electronic message contains information which may be confidential or p= rivileged. The information is intended for the use of the individual or ent= ity named above. If you are not the intended recipient, be aware that any d= isclosure, copying, distribution or use of the contents of this information= is prohibited. If you have received this electronic transmission in error,= please notify us by e-mail at (postmaster@rapid7.com) immediately. --_000_72199978CE4FB345A2A454C6FEAAB425186D0CA3BOSTONEXtorrapi_ Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable
It looks like I can infer this from the local table in the system sc= hema by looking at the datacenter value.

Would this be a bad bad thing to do?

Thanks,
Ben
From: Ben Boule [Ben_Boule@rapid7.com]
Sent: Tuesday, July 30, 2013 11:41 AM
To: user@cassandra.apache.org
Subject: Determining Snitch at Runtime

Hi Everyone,

Sorry if the answer to this question is out there, I can't seem to find it = by searching.

Is there a way to read the endpoint_snitch at runtime, preferably from a CQ= L query, but fine if it's available through an older API?   (Or J= MX?)

We're automating creating clusters & provisioning our schema appropriat= ely into them, it'd be great if the provisioning program could figure this = out once it connected to the cluster before creating keyspaces.  Right= now we are having to track a maze of parameters to make sure that the cluster gets created with the right snitch, and then= that we can pass a parameter into the provisioning program to tell it whic= h topology strategy to use.

Thank you,
Ben

This electronic message contains information which may be confidential o= r privileged. The information is intended for the use of the individual or = entity named above. If you are not the intended recipient, be aware that an= y disclosure, copying, distribution or use of the contents of this information is prohibited. If you have rece= ived this electronic transmission in error, please notify us by e-mail at (= postmaster@rapid7.com) immediately.

This electronic message contains information which may be confidential o= r privileged. The information is intended for the use of the individual or = entity named above. If you are not the intended recipient, be aware that an= y disclosure, copying, distribution or use of the contents of this informat= ion is prohibited. If you have received this electronic transmission in err= or, please notify us by e-mail at (postmaster@rapid7.com) immediately.

<= /body> --_000_72199978CE4FB345A2A454C6FEAAB425186D0CA3BOSTONEXtorrapi_--