Well, Amazon is expensive. Hetzner will sell you dedicated SSD RAID-1 servers
with 32GB RAM and 4 cores with HT for €59/mth. However, if pricing is an
issue, you could start with:
1 server : read at ONE, write at ONE, RF=1. You will have consistency, but not
high availability. This is the
how many nodes to start with(2 ok?) ?
I'd recommend 3, that will give you some redundancy see
http://thelastpickle.com/2011/06/13/Down-For-Me/
Cheers
-
Aaron Morton
Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 5/08/2013, at 1:41 AM, Rajkumar
From what I understood tons of people are running things on ec2, but it
could be the instance size is pretty large that it compares to a dedicated
server (especially if you go with SSD, it is like 1K/month!)
On Tue, Aug 6, 2013 at 3:54 AM, Aaron Morton aa...@thelastpickle.comwrote:
how many
3 node EC2 m1.xlarge is ~ $1000/k month + any incidental costs ( s3
backups, transfer out of the AZ ), etc ) or ~$300/month after a ~$1400
upfront 1 year reservation fee.
There are some uncomfortable spots when compaction kicks on concurrently
for several large CF's but otherwise its been
Amazon seems to much overprice its services. If you look out for a similar
size deployment elsewhere like linode or digital ocean(very competitive
pricing), you'll notice huge differences. Ok, some services features are
extra but may we all don't need them necessarily when you can host on
We run a cluster in EC2 and it's working very well for us. The standard
seems to be M2.2XLarge instances with data living on the ephemeral drives
(which means its local and fast) and backups either to EBS, S3 or just
relying on cluster size and replication (we avoid that last idea).
Brian
On
@David:
Like all other start-ups, we too cannot start with all dedicated servers
for Cassandra. So right now we have no better choice except for using a VPS
:), but we can definitely choose one from amongst a suitable set of VPS
configurations. As of now since we are starting out, could we
with 2 GB RAM be prepared to expect crashes because it hardly can handle
peaks with increased memory consumption by compaction, validation, etc.
KVM works good only if you are using recent version and virtio drivers
and provider is not overselling memory. At shared hosting you will not
be able
okay, so what should a workable VPS configuration to start with minimum
how many nodes to start with(2 ok?) ? Seriously I cannot afford the
tensions of colocation setup. My hosting provider provides SSD drives with
KVM virtualization.
Of course -- my point is simply that if you're looking for speed, SSD+KVM,
especially in a shared tenant situation, is unlikely to perform the way you
want to. If you're building a pure proof of concept that never stresses the
system, it doesn't matter, but if you plan an MVP with any sort of
workable configuration depends on your requirements. You need to develop
own testing procedure.
How much data will have
whats 95 percentile response time target
size of rows
number of columns per row
data grow rate
data rewrite rate
ttl expiration used
never aim for minimum. Cassandra has huge
If you want to get a rough idea of how things will perform, fire up YCSB
(https://github.com/brianfrankcooper/YCSB/wiki) and run the tests that closest
match how you think your workload will be (run the test clients from a couple
of beefy AWS spot-instances for less than a dollar). As you are a
I am building a cluster(initially starting with a 2-3 nodes cluster). I
have came across two seemingly good options for hosting, Linode Digital
Ocean. VPS configuration for both listed below:
Linode:-
--
XEN Virtualization
2 GB RAM
8 cores CPU (2x priority) (8 processor Xen
I've run several lab configurations on linodes; I wouldn't run cassandra on any
shared virtual platform for large-scale production, just because your IO
performance is going to be really hard to predict. Lots of people do, though
-- depends on your cassandra loads and how consistent you need
14 matches
Mail list logo
