*Tuesday, May 23, 2017 at 1:52 PM
> *To: *"user@cassandra.apache.org"
> *Subject: *Re: EC2 instance recommendations
>
>
>
> Yes we can only reboot.
>
> But using rf=2 or higher it's only a node fresh restart.
>
> EBS is a network attached disk. Spinning
data will get replicated when
> it’s brought up?
>
>
>
> *From: *Cogumelos Maravilha
> *Date: *Tuesday, May 23, 2017 at 1:52 PM
> *To: *"user@cassandra.apache.org"
>
> *Subject: *Re: EC2 instance recommendations
>
>
>
> Yes we can only reboot.
&g
, Bhuvan Rawal
mailto:bhu1ra...@gmail.com>>
Cc: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: EC2 instance recommendations
> Oh, so all the data is lost if the instance is shutdown or restarted (for
&
ija Gobec
> mailto:matija0...@gmail.com>>, Bhuvan Rawal
> mailto:bhu1ra...@gmail.com>>
> *Cc: *"user@cassandra.apache.org
> <mailto:user@cassandra.apache.org>" <mailto:user@cassandra.apache.org>>
>
>
>
more expensive than an I3.
>
>
>
> *From: *Jonathan Haddad
> *Date: *Tuesday, May 23, 2017 at 9:42 AM
> *To: *"Gopal, Dhruva" , Matija Gobec <
> matija0...@gmail.com>, Bhuvan Rawal
> *Cc: *"user@cassandra.apache.org"
>
>
> *Subject:
;>
>> *Date: *Tuesday, May 23, 2017 at 9:42 AM
>> *To: *"Gopal, Dhruva" , Matija Gobec <
>> matija0...@gmail.com>, Bhuvan Rawal
>>
>> *Cc: *"user@cassandra.apache.org"
>>
>>
>> *Subject: *Re: EC2 instance recommendat
oach to backing up the directory,
> and restoring it, if we ever have to bring down the instance and back up,
> will that work as a strategy? Data is only kept around for 2 days and is
> TTL’d after.
>
>
>
> *From: *Matija Gobec
> *Date: *Tuesday, May 23, 2017 at 8:15 AM
&
p the directory,
> and restoring it, if we ever have to bring down the instance and back up,
> will that work as a strategy? Data is only kept around for 2 days and is
> TTL’d after.
>
>
>
> *From: *Matija Gobec
> *Date: *Tuesday, May 23, 2017 at 8:15 AM
> *To: *Bhuvan
at a
reasonable rate, it gets more expensive than an I3.
From: Jonathan Haddad
Date: Tuesday, May 23, 2017 at 9:42 AM
To: "Gopal, Dhruva" , Matija Gobec
, Bhuvan Rawal
Cc: "user@cassandra.apache.org"
Subject: Re: EC2 instance recommendations
> Oh, so all the data is
after.
>>
>>
>>
>> *From: *Matija Gobec
>> *Date: *Tuesday, May 23, 2017 at 8:15 AM
>> *To: *Bhuvan Rawal
>> *Cc: *"Gopal, Dhruva" , "
>> user@cassandra.apache.org"
>> *Subject: *Re: EC2 instance recommendations
>>
&g
L’d after.
>
>
>
> *From: *Matija Gobec
> *Date: *Tuesday, May 23, 2017 at 8:15 AM
> *To: *Bhuvan Rawal
> *Cc: *"Gopal, Dhruva" , "
> user@cassandra.apache.org"
> *Subject: *Re: EC2 instance recommendations
>
>
>
> We are running on I3s sin
TTL’d after.
From: Matija Gobec
Date: Tuesday, May 23, 2017 at 8:15 AM
To: Bhuvan Rawal
Cc: "Gopal, Dhruva" , "user@cassandra.apache.org"
Subject: Re: EC2 instance recommendations
We are running on I3s since they came out. NVMe SSDs are really fast and I
managed to push
We are running on I3s since they came out. NVMe SSDs are really fast and I
managed to push them to 75k IOPs.
As Bhuvan mentioned the i3 storage is ephemeral. If you can work around it
and plan for failure recovery you are good to go.
I ran Cassandra on m4s before and had no problems with EBS volum
i3 instances will undoubtedly give you more meat for buck - easily 40K+
iops whereas on the other hand EBS maxes out at 20K PIOPS which is highly
expensive (at times they can cost you significantly more than cost of
instance).
But they have ephemeral local storage and data is lost once instance is
14 matches
Mail list logo
