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 2A0E4186F7 for ; Fri, 21 Aug 2015 09:38:23 +0000 (UTC) Received: (qmail 89217 invoked by uid 500); 21 Aug 2015 09:38:19 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 89170 invoked by uid 500); 21 Aug 2015 09:38:19 -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 89160 invoked by uid 99); 21 Aug 2015 09:38:19 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2015 09:38:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id B349AC08D9 for ; Fri, 21 Aug 2015 09:38:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7dyPx45O16-a for ; Fri, 21 Aug 2015 09:38:02 +0000 (UTC) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id DC28454ADB for ; Fri, 21 Aug 2015 09:38:01 +0000 (UTC) Received: by lahi9 with SMTP id i9so37874941lah.2 for ; Fri, 21 Aug 2015 02:38:00 -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=u0M3d0Q4MLVxg/CMBqHoiDEJ8HPc00dCv1P0nGO/Cdc=; b=jp1mWi2HknVk8L1Ljk5PljD8yIOnx5a+RH7ccKnO+2ShAdSqnhI5wgIPDRlNsilQD6 SDhd+tvRldDyFIAJ67dJPC459tQC6v+CNp4hj0TsOlQUxHbF4epJUapP2GavGl7CuOvT 5Fm5K5qB3M4h8ertfEkkLr0ERjYZ75pxyUIRTC9/neOf0sR1SJ1pUGzTdmha3V+hBFA4 xiIcvSKqSA0dNT+Dg96vwikKMgfT2cGtvRoTrItMcsQOem19+CvIbaemsMF8jAutZVx0 B7PQUz0oxOqBrRQRTBvrwE6F8BeCr+wJZPoWtfrp0evG5Ob3KQASFsX4voQ16ZdUmuHP X8lw== X-Received: by 10.112.176.228 with SMTP id cl4mr7110250lbc.106.1440149880748; Fri, 21 Aug 2015 02:38:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.208.104 with HTTP; Fri, 21 Aug 2015 02:37:41 -0700 (PDT) In-Reply-To: References: From: Alain RODRIGUEZ Date: Fri, 21 Aug 2015 11:37:41 +0200 Message-ID: Subject: Re: GossipingPropertyFileSnitch vs Ec2Snitch To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1133a02e10c26a051dcf06f6 --001a1133a02e10c26a051dcf06f6 Content-Type: text/plain; charset=UTF-8 Hi guys, I am also wondering about this kind of stuff, since we are going out of AWS and were using EC2Snitch. I felt free to write it here, since it looks linked to previous comments. @John, we have been using EC2Snitch for many years, and it just works fine ! Plus, we don't have to keep the GPFS file up to date every time we add a node or remove one. EC2Snitch is quite strait-forward and easy to use. The first "issue" we have today, is indeed to add a new DC from outside AWS. I am trying to find out how to do that right now. If we figure out that this is easy, you can perfectly go with EC2Snitch imho. So what would be the procedure to go from EC2Snitch to GPFS ? I see 2 possibilities and I am not sure of the result of each of these: - Node by node, on a rolling restart way, and making sure that you use the former DC names and racks. Copying the EC2 network. Would this be doable or would that need a full cluster restart at once ? - Add the new DC using directly GPFS on all the node without modifying the old one (hybride: 1 DC EC2Snitch, 1 DC GPFS), again copying the EC2 DCs and racks. Would this work ? Also, Is this need of mirroring the exact DC and racks name mandatory in those 2 procedures as I think it is ? I think this worth a good testing anyway. C*heers, Alain 2015-08-03 22:04 GMT+02:00 John Wong : > Thanks Rob. > > But even if we do move out of EC2 in X years, unlike partitioner, I don't > think there is much to do to switch snitch. Yes, I am evaluating if there > is actually good benefit to use EC2. > > John > > On Mon, Aug 3, 2015 at 1:54 PM, Robert Coli wrote: > >> On Sun, Aug 2, 2015 at 6:22 PM, John Wong wrote: >> >>> What other benefits can Ec2Snitch provide in a single-region, multi-az >>> AWS deployment besides automatically setting dc and rack for you as the >>> snitch reads from EC2 metadata. >>> Obviously there is a concern with what if there is something wrong with >>> the metadata server... >>> >> >> GPFS is broadly similar to EC2Snitch/EC2MRSnitch, but is usable if you >> for example have a DR site outside of EC2. >> >> In general I'd probably suggest using GPFS unless you're really sure >> you'll always be in EC2, forever and always. >> >> =Rob >> >> > > --001a1133a02e10c26a051dcf06f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi guys,

I am also wondering about this= kind of stuff, since we are going out of AWS and were using EC2Snitch. I f= elt free to write it here, since it looks linked to previous comments.

@John, we have been using EC2Snitch for many years, an= d it just works fine ! Plus, we don't have to keep the GPFS file up to = date every time we add a node or remove one. EC2Snitch is quite strait-forw= ard and easy to use. The first "issue" we have today, is indeed t= o add a new DC from outside AWS. I am trying to find out how to do that rig= ht now. If we figure out that this is easy, you can perfectly go with EC2Sn= itch imho.

So what would be the procedure to = go from EC2Snitch to GPFS ?

I see 2 possibilities = and I am not sure of the result of each of these:

= - Node by node, on a rolling restart way, and making sure that you use the = former DC names and racks. Copying the EC2 network. Would this be doable or= would that need a full cluster restart at once ?
- Add the new D= C using directly GPFS on all the node without modifying the old one (hybrid= e: 1 DC EC2Snitch, 1 DC GPFS), again copying the EC2 DCs and racks. Would t= his work ?

Also, Is this need of mirroring the exa= ct DC and racks name mandatory in those 2 procedures as I think it is ?

I think this worth a good testing anyway.
=

C*heers,

Alain

2015-08-03 22:04 GMT+= 02:00 John Wong <gokoproject@gmail.com>:
Thanks Rob.

But even= if we do move out of EC2 in X years, unlike partitioner, I don't think= there is much to do to switch snitch. Yes, I am evaluating if there is act= ually good benefit to use EC2.

John

On Mon, Aug 3, 2015 at 1:54 PM, Robert Coli <rcoli@eventbrite.com= > wrote:
<= div class=3D"gmail_extra">
On Sun, Aug 2, 2= 015 at 6:22 PM, John Wong <gokoproject@gmail.com> wrote:=
Wha= t other benefits can Ec2Snitch provide in a single-region, multi-az AWS dep= loyment besides automatically setting dc and rack for you as the snitch rea= ds from EC2 metadata.
Obviously there is a concern wit= h what if there is something wrong with the metadata server...

GPFS is broadly similar to EC2Sn= itch/EC2MRSnitch, but is usable if you for example have a DR site outside o= f EC2.

In general I'd probably suggest using G= PFS unless you're really sure you'll always be in EC2, forever and = always.

=3DRob
=C2=A0
<= /div>


--001a1133a02e10c26a051dcf06f6--