HI
We have 2 - 3 installations with single node Cassandra. They working fine,
no problems there,
except if Cassandra stops, everything stops. Even on one node, we usually
"rolling" 500-600 GB data, sometimes even 2-3 TB. We use mostly standard
configuration with almost no changes there.
Here are
And I think in a 3 node cluster, RAID 0 would do the job instead of RAID 5 . So
you will need less storage to get same disk space. But you will get protection
against disk failures and infact entire node failure.
Anuj
Sent from Yahoo Mail on Android
On Sat, 23 Jan, 2016 at 10:30 am, Anuj Wa
I think Jonathan said it earlier. You may be happy with the performance for now
as you are using the same commitlog settings that you use in large clusters.
Test the new setting recommended so that you know the real picture. Or be
prepared to lose some data in case of failure.
Other than durabil
You do of course have the simple technical matters, most of which need to
be addressed with a proof of concept implementation, related to memory,
storage, latency, and throughput. I mean, with a scaled cluster you can
always add nodes to increase capacity and throughput, and reduce latency,
but wit
ssandra is in its replication – as a single node
>>> solution, it’s slower and less flexible than alternatives
>>>
>>
>>
>>>
>>> From: John Lammers
>>> Reply-To: "user@cassandra.apache.org"
>>> Date: Friday, January 22, 2016 at 12:57 P
Thanks for your response Jack.
We are already sold on distributed databases, HA and scaling. We just have
some small deployments coming up where there's no money for servers to run
multiple Cassandra nodes.
So, aside from the lack of HA, I'm asking if a single Cassandra node would
be viable in a
>>
>
>
>>
>> From: John Lammers
>> Reply-To: "user@cassandra.apache.org"
>> Date: Friday, January 22, 2016 at 12:57 PM
>> To: Cassandra Mailing List
>>
>> Subject: Fwd: Production with Single Node
>>
>> Thanks for your reply Sebastian
gt; Reply-To: "user@cassandra.apache.org"
>> Date: Friday, January 22, 2016 at 12:57 PM
>> To: Cassandra Mailing List
>>
>> Subject: Fwd: Production with Single Node
>>
>> Thanks for your reply Sebastian.
>>
>> They are specialized d
solution,
> it’s slower and less flexible than alternatives
>
> From: John Lammers
> Reply-To: "user@cassandra.apache.org"
> Date: Friday, January 22, 2016 at 12:57 PM
> To: Cassandra Mailing List
>
> Subject: Fwd: Production with Single Node
>
> Th
er and less flexible than alternatives
>
>
> From: John Lammers
> Reply-To: "user@cassandra.apache.org"
> Date: Friday, January 22, 2016 at 12:57 PM
> To: Cassandra Mailing List
>
> Subject: Fwd: Production with Single Node
>
> Thanks for your reply Se
The value of cassandra is in its replication – as a single node solution, it’s
slower and less flexible than alternatives
From: John Lammers
Reply-To: "user@cassandra.apache.org"
Date: Friday, January 22, 2016 at 12:57 PM
To: Cassandra Mailing List
Subject: Fwd: Production with S
need ammo to
convince others. Or failing that, what can be done to make this
configuration as safe & robust as possible?
Thanks!
--John
-- Forwarded message --
From: Sebastian Estevez
Date: Fri, Jan 22, 2016 at 3:41 PM
Subject: Fwd: Production with Single Node
To: j
I could see this being desirable if you are deploying the exact same
application as you deploy in other places with many nodes, and you know the
load will be low. It may be a rare situation but in such a case you save
big effort by not having to change your application logic.
Not that I necessaril
challenge now is a new market consisting of many small sites that
reportedly can't afford a multi-server solution. These would be permanent,
one node systems.
--John
-- Forwarded message --
From: Jonathan Haddad
Date: Fri, Jan 22, 2016 at 3:34 PM
Subject: Re: Production
My opinion:
http://rustyrazorblade.com/2013/09/cassandra-faq-can-i-start-with-a-single-node/
TL;DR: the only reason to run 1 node in prod is if you're super broke but
know you'll need to scale up almost immediately after going to prod (maybe
after getting some funding).
If you're planning on doin
The risks would be about the same as with a single-node Postgres or MySQL
database, except that you wouldn't have the benefit of full SQL.
How much data (rows, columns), what kind of load pattern (heavy write,
heavy update, heavy query), and what types of queries (primary key-only,
slices, filteri
After deploying a number of production systems with up to 10 Cassandra
nodes each, we are looking at deploying a small, all-in-one-server system
with only a single, local node (Cassandra 2.1.11).
What are the risks of such a configuration?
The virtual disk would be running RAID 5 and the disk con
17 matches
Mail list logo
