Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4C413200BB6 for ; Fri, 4 Nov 2016 11:59:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4ADF7160AE9; Fri, 4 Nov 2016 10:59:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 45DF6160AE8 for ; Fri, 4 Nov 2016 11:59:58 +0100 (CET) Received: (qmail 4197 invoked by uid 500); 4 Nov 2016 10:59:56 -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 4187 invoked by uid 99); 4 Nov 2016 10:59:56 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2016 10:59:56 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5613EC7A4F for ; Fri, 4 Nov 2016 10:59:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 1teoBE1MG7on for ; Fri, 4 Nov 2016 10:59:54 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 015735F3BB for ; Fri, 4 Nov 2016 10:59:53 +0000 (UTC) Received: by mail-wm0-f45.google.com with SMTP id a197so42891076wmd.0 for ; Fri, 04 Nov 2016 03:59:53 -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; bh=bgXz9cBrGPpJIbHPV7zpx+lQiPahh8byw3DSQBzzCwk=; b=Ho4lOOAfONWdrtSr6TngOgudHspRxXrRts5WmohK/lEnPJtjkIyyj1w9QmOE/xb6GK XmjyhsY59tKppRUQLUGBn5MElklLYkFptCUuXSW4iqN1/JieFOSxgc8Ur9JHgCoyhUBO x16f3VVLJAOiIEh3amytc3kqWLIZat0UHUilYjzBnfi46FeH1M9o+r1bNT69kc2d3lAY bTdWAu2Bu95DbfGatSdkAeRwxtlPiwswjfDHHDNSHP0/M9oPDutfgqbEx/TD81vooCcQ +1UDRlg3Nou7trTpT9TB4vVARwjjsP9ZRDMkVlFlF8vyZXV4j/3dJpm2MVFpmoPxpH/J Rcug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=bgXz9cBrGPpJIbHPV7zpx+lQiPahh8byw3DSQBzzCwk=; b=csyofcOOZcVV88znJ8cQUxvvxH80zbGeLHqBHcqoR+XfQDMqbZRqwB9O9KrPR69UcT lpuG2+gveDChq32HFmDM9D87ATvRbkRdZbtAO0aVuivwpZdIZLkpQE2saAc7aL+herRC 3IrG4wTUId6Mqbvy0uOMlVqpRSNw01blQMQUS7kW37E2s7ebM6LUexEmsT7P/YbGOVST cwjMqRTOVpT+Ccd8V5/cKzuPLqseJSHvc4bscc72JhqiUG+KVj4q90FwQtJQhWDtcL2e KiRAio41XAGlInXIiqyesTeRntoEk0tm+mvenwod5URXJWGnfzydyB+II8RhrptShuwN isUg== X-Gm-Message-State: ABUngveZkWJOIcoX6a5uN775ntAM4pl4aPQA6IvwLhWMMG/2rE/bF3PTMab/EZP8h7ngscyzsdLepzPMd8w3vw== X-Received: by 10.194.149.143 with SMTP id ua15mr4212077wjb.48.1478257192790; Fri, 04 Nov 2016 03:59:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.132.7 with HTTP; Fri, 4 Nov 2016 03:59:52 -0700 (PDT) In-Reply-To: <1582ee2e6cf.d5ca524421325.4963512365134511810@winguzone.com> References: <1582ee2e6cf.d5ca524421325.4963512365134511810@winguzone.com> From: Oskar Kjellin Date: Fri, 4 Nov 2016 11:59:52 +0100 Message-ID: Subject: Re: Cassandra on Cloud platforms experience To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e0122897cdcf11b054077920e archived-at: Fri, 04 Nov 2016 10:59:59 -0000 --089e0122897cdcf11b054077920e Content-Type: text/plain; charset=UTF-8 It is good enough if you do not care about automation. If you care about automation (and you really should), GossipPropertyFileSnitch is not good enough as it has to be manually updated. Same with availability set, fault domain isn't available for the instance as metadata as it is on AWS. You still have a global limit for the storage account IOPS. So even tho you might get thruput with a few servers, adding more means copying the VHD to multiple storage accounts, making automation once again cumbersome. 2016-11-04 11:29 GMT+01:00 Vladimir Yudovin : > Hi, > > >1. No native snitch > It's not great problem. GossipPropertyFileSnitch is good enough. > > >2. No concept of availability zones. > Azure does have such concept - Availability Set. > > It provides three fault domain (availability zone in Amazon terms) and 20 > updates domains. > > >4. Even running SSDs will give you poor performance. > It depends on disk size. 1T SSD provides 5000 IOPS. > > > So in short: > Amazon - provides data at rest encryption, flexible EBS storage (or local > disks), availability zones. > Azure - provides data at rest encryption, less flexible storage (or local > disks), availability zones. > SoftLayer - no data encryption, but they have unique feature - > connectivity between different data centers (they call this VLAN spanning) > without need in VPN or other tunneling. They don't have explicit AV zones, > but you can put nodes in different DC in the same region (some locations) > with relative low latency 1-1.5 ms. or purchase another VLAN in different > pod for $25 per month in the same DC. > > We provide Cassandra cluster on all provider in many worldwide locations. > > Best regards, Vladimir Yudovin, > > *Winguzone - Hosted Cloud > CassandraLaunch your cluster in minutes.* > > > ---- On Fri, 04 Nov 2016 05:10:06 -0400*Oskar Kjellin > >* wrote ---- > > So I've run Cassandra on both Aws and azure. I would strongly suggest that > if you have the option, run as far away from azure as you can. > > Here's a list of issues I have running Cassandra on azure: > 1. No native snitch > 2. No concept of availability zones. This makes it impossible for > Cassandra to put replicas in different AZs. This will hurt your uptime and > might incur loss of data. (They have something called a fault domain tho) > 3. The disks have iops that land in the floppy disk range > 4. Even running SSDs will give you poor performance. > 5. Beware of the global storage account limit. This makes scaling out hurt > performance if you put them on the same storage account. Which if your > using images is your only choice. > > Sent from my iPhone > > > On 4 nov. 2016, at 00:22, cass savy wrote: > > > > I would like to hear from the community on their experiences or lesson > learnt on hosting Cassandra in cloud platforms like > > > > 1. Google Cloud Platform > > 2. AWS > > 3. Azure > > > > 1. Which cloud hosting is better and Why? > > 2. What differences of C* over vendor provided NoSQL DB like (Bigtable, > Dynamo,Azure Document DB) > > 3. AWS is more mature in his offerings and Azure is getting there or its > there already based on what I have been investigating so far? > > > > 4. What is drive to pick one vs another -Is it cost, infrastructure, > hardware SKU, availability, scalability, performance,ease of deployment and > maintenance,..etc? > > > > Please let me know your thoughts and suggestions if somebody has done a > deep dive into these 3 cloud platforms for C*. > > > > > > We use datastax cassandra and exploring new usecases in AWS and also > evaluating or POC it in Azure/GCP > > > > > --089e0122897cdcf11b054077920e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is good enough if you do not care about automation.If you care about automation (and you really should),=C2=A0GossipP= ropertyFileSnitch is not good enough as it has to be manually updated. Same= with availability set, fault domain isn't available for the instance a= s metadata as it is on AWS.

= You still have a global limit for the storage account IOPS. So even tho you= might get thruput with a few servers, adding more means copying the VHD to= multiple storage accounts, making automation once again cumbersome.
<= /div>

2016-11-04 1= 1:29 GMT+01:00 Vladimir Yudovin <vladyu@winguzone.com>:
Hi,

<= /div>
>1. No native snitch
It&#= 39;s not great problem. GossipPropertyFileSnitch is good enough.
=

>2. No concept of avai= lability zones.
Azure does have such concept - = Availability Set. It provides three fault domain (availability z= one in Amazon terms) and 20 updates domains.

>4. Even running SSDs will give you poor performa= nce.
It depends on disk size. 1T SSD provides 5= 000 IOPS.


So in short:
Amazon - provides data at rest encryption, flexible EBS storage (or l= ocal disks), availability zones.
Azure - provides data at res= t encryption, less flexible storage (or local disks), availability zones.
SoftLayer - no data encryption, but they have unique feature -= connectivity between different data centers (they call this VLAN spanning)= without need in VPN or other tunneling. They don't have explicit AV zo= nes, but you can put nodes in different DC in the same region (some locatio= ns) with relative low latency 1-1.5 ms. or purchase another VLAN in differe= nt pod for $25 per month in the same DC.

We pr= ovide Cassandra cluster on all provider in many worldwide locations.

Best regards, Vlad= imir Yudovin,
Winguzone - Hosted Cloud Cassandra
Launch your = cluster in minutes.


---- On Fri, 04 Nov 2016 05:10:06 -0400Oskar Kjellin <oskar.kjellin@gmail.com> wrote ----

<= blockquote style=3D"border-left:1px solid #cccccc;padding-left:6px;margin:0= 0 0 5px">
So I've run Cassandra on both Aws and azure. I woul= d strongly suggest that if you have the option, run as far away from azure = as you can.

Here's a list of issues I hav= e running Cassandra on azure:
1. No native snitch
=
2. No concept of availability zones. This makes it impossible for Cass= andra to put replicas in different AZs. This will hurt your uptime and migh= t incur loss of data. (They have something called a fault domain tho)
<= /div>
3. The disks have iops that land in the floppy disk range
4. Even running SSDs will give you poor performance.
5. Beware of the global storage account limit. This makes scaling out hurt= performance if you put them on the same storage account. Which if your usi= ng images is your only choice.

Sent from my i= Phone

>
> I would like t= o hear from the community on their experiences or lesson learnt on hosting = Cassandra in cloud platforms like
>
> 1= . Google Cloud Platform
> 2. AWS
> 3. A= zure
>
> 1. Which cloud hosting is bet= ter and Why?
> 2. What differences of C* over vendor pro= vided NoSQL DB like (Bigtable, Dynamo,Azure Document DB)
>= ; 3. AWS is more mature in his offerings and Azure is getting there or its = there already based on what I have been investigating so far?
>
> 4. What is drive to pick one vs another -Is it c= ost, infrastructure, hardware SKU, availability, scalability, performance,e= ase of deployment and maintenance,..etc?
>
> Please let me know your thoughts and suggestions if somebody has done= a deep dive into these 3 cloud platforms for C*.
>
<= /div>
>
> We use datastax cassandra and exploring = new usecases in AWS and also evaluating or POC it in Azure/GCP
<= div>>


--089e0122897cdcf11b054077920e--