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 9DBC3C19F for ; Thu, 5 Jun 2014 12:13:00 +0000 (UTC) Received: (qmail 72754 invoked by uid 500); 5 Jun 2014 12:12:58 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 72721 invoked by uid 500); 5 Jun 2014 12:12:58 -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 72713 invoked by uid 99); 5 Jun 2014 12:12:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 12:12:58 +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 arodrime@gmail.com designates 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 12:12:52 +0000 Received: by mail-lb0-f182.google.com with SMTP id z11so499832lbi.41 for ; Thu, 05 Jun 2014 05:12:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=eh+kT3OzKRSkh2z+hICyT7v874FQGzvWWeCW4OB2OIU=; b=cylWmbTzj0FF098zr0r0TxQVseP3c/XikLudQZ4g25GrZmxkG3qCiOjVTUBP0Ybb1K 7XfEnSjmSAsp+3E223yJ5D+Yp+F8FiWBpyGTWYg1FM2hWjkXMUzQeXRNTNlenZK6bcbT eHUP7++/Cw+9HBkZyHQ8P3Q4ouMK3SPyfnjNRTgq3nAycw3lZXH9Ik0XYFJG5R8TrMlG qqr4DyJ8DDOIuCP/31bL6WtZsXRd1pbMUxdiHBUv9/xBf7CJzy8n5dk5YDyf9S9vtVC1 WMW32OY7dwVmIBKHgD+8CXkDaUckjxeT9vlPMlIO5Ytde34Mj89D18flKAJ+78WkKExy cs+A== X-Received: by 10.152.234.229 with SMTP id uh5mr19730847lac.56.1401970351391; Thu, 05 Jun 2014 05:12:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.215.106 with HTTP; Thu, 5 Jun 2014 05:12:11 -0700 (PDT) From: Alain RODRIGUEZ Date: Thu, 5 Jun 2014 14:12:11 +0200 Message-ID: Subject: VPC AWS To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1133a6fac7cbc204fb15a85c X-Virus-Checked: Checked by ClamAV on apache.org --001a1133a6fac7cbc204fb15a85c Content-Type: text/plain; charset=ISO-8859-1 Hi guys, We are going to move from a cluster made of simple Amazon EC2 servers to a VPC cluster. We are using Cassandra 1.2.11 and I have some questions regarding this switch and the Cassandra configuration inside a VPC. Actually I found no documentation on this topic, but I am quite sure that some people are already using VPC. If you can point me to any documentation regarding VPC / Cassandra, it would be very nice of you. We have only one DC for now, but we need to remain multi DC compatible, since we will add DC very soon. Else, I would like to know if I should keep using EC2MultiRegionSnitch or change the snitch to anything else. What about broadcast/listen ip, seeds...? We currently use public ip as for broadcast address and for seeds. We use private ones for listen address. Machines inside the VPC will only have private IP AFAIK. Should I keep using a broadcast address ? Is there any other incidence when switching to a VPC ? Sorry if the topic was already discussed, I was unable to find any useful information... --001a1133a6fac7cbc204fb15a85c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

We are going to move from a cl= uster made of simple Amazon EC2 servers to a VPC cluster. We are using Cass= andra 1.2.11 and I have some questions regarding this switch and the Cassan= dra configuration inside a VPC.

Actually I found no documentation on this topic, but I = am quite sure that some people are already using VPC. If you can point me t= o any documentation regarding VPC / Cassandra, it would be very nice of you= . We have only one DC for now, but we need to remain multi DC compatible, s= ince we will add DC very soon.

Else, I would like to know if I should keep using EC2Mu= ltiRegionSnitch or change the snitch to anything else.

=
What about broadcast/listen ip, seeds...?

We currently use public ip as for broadcast address and for seeds. We use p= rivate ones for listen address. Machines inside the VPC will only have priv= ate IP AFAIK. Should I keep using a broadcast address ?

Is there any other incidence when switching to a VPC ?

<= /div>
Sorry if the topic was already discussed, I was unable to find an= y useful information...
--001a1133a6fac7cbc204fb15a85c--