Internode speculative retry is on by default with p99
The client side retry varies by driver / client
> On Oct 17, 2021, at 1:59 PM, S G wrote:
>
>
>
> "The harder thing to solve is a bad coordinator node slowing down all reads
> coordinated by that node"
> I think this is the root of the
Also, for the percentile based speculative retry, how big of a time-period
is used to calculate the percentile?
If it is only a few seconds, then the latency will increase very quickly
when server performance degrades.
But if it is upto a few minutes (or it is configurable), then its
percentile wil
"The harder thing to solve is a bad coordinator node slowing down all reads
coordinated by that node"
I think this is the root of the problem and since all nodes act as
coordinator nodes, so it guaranteed that if any 1 node slows down (High GC,
Segment Merging etc), it will slow down 1/N queries in
Some random notes, not necessarily going to help you, but:
- You probably have vnodes enable, which means one bad node is PROBABLY a
replica of almost every other node, so the fanout here is worse than it
should be, and
- You probably have speculative retry on the table set to a percentile. As
the
Hello,
We have frequently seen that a single bad node running slow can affect the
latencies of the entire cluster (especially for queries where the slow node
was acting as a coordinator).
Is there any suggestion to avoid this behavior?
Like something on the client side to not query that bad nod
On Fri, Jul 30, 2021 at 7:21 PM Bowen Song wrote:
> Since you have only one node, sstableloader is unnecessary. Copy/move the
> the data directory back to the right place and restart Cassandra or run
> 'nodetool
> refresh' is sufficient. Do not restore the 'system' keyspace, but do
> restore the
local-7ad54392bcdd35a684174e047860b377'
4. change num_tokens
5. start Cassandra
On 30/07/2021 17:00, Maxim Parkachov wrote:
Thanks for quick answer.
Do you ever intend to add nodes to this single node cluster? If
not, I don't see the number of tokens matter at all.
I unde
Thanks for quick answer.
> Do you ever intend to add nodes to this single node cluster? If not, I
> don't see the number of tokens matter at all.
>
I understand that, I would like to have all environments with the same
settings.
> However, if you really want to change it and do
Do you ever intend to add nodes to this single node cluster? If not, I
don't see the number of tokens matter at all.
However, if you really want to change it and don't mind downtime, you
can do this:
1. make a backup of the data
2. completely destroy the node with all data i
Single node does not make any sense in Cassandra. It should not make any
difference with a single node with whatever number of tokens you start
with. You can change your tokens on the test server and see what happens.
On Fri, Jul 30, 2021 at 5:53 PM Maxim Parkachov
wrote:
> Hi everyone,
&g
Hi everyone,
I have several development servers with 1 node and num_tokens 256. As
preparation for testing 4.0 I would like to change num_tokens to 16.
Unfortunately I could not add any additional nodes or additional DC, but
I'm fine with downtime. The important part, data should be preserved.
Wh
> On Apr 9, 2021, at 6:15 AM, Joe Obernberger
> wrote:
>
>
> We run a ~1PByte HBase cluster on top of Hadoop/HDFS that works pretty well.
> I would love to be able to use Cassandra instead on a system like that.
>
1PB is definitely in the range of viable cassandra clusters today
> Even
his hosts.
>>
>> Problem is, while I usually use a cluster of 6 "smallish" nodes (which
>> can grow in time), he only has big ESX servers with huge disk space (which
>> is already RAID-6 redundant) but wouldn't have the possibility to have 3+
>
available in the
open source version, too.
Sean Durity – Staff Systems Engineer, Cassandra
From: Elliott Sims
Sent: Thursday, April 8, 2021 6:36 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Huge single-node DCs (?)
I'm not sure I'd suggest building a single DIY Backblaze
ibility to have 3+ nodes per DC.
This is out of my usual experience with Cassandra and, as far as
I read around, out of most use-cases found on the website or
this mailing list, so the question is:
does it make sense to use Cassandra with a big (let's talk 6TB
today, up
ot; nodes (which can
> grow in time), he only has big ESX servers with huge disk space (which is
> already RAID-6 redundant) but wouldn't have the possibility to have 3+
> nodes per DC.
>
> This is out of my usual experience with Cassandra and, as far as I read
> around,
es found on the website or this
mailing list, so the question is:
does it make sense to use Cassandra with a big (let's talk 6TB today,
up to 20TB in a few years) single-node DataCenter, and another
single-node DataCenter (to act as disaster recovery)?
Thanks in advance for any suggestion or comment!
use Cassandra with a big (let's talk 6TB today,
up to 20TB in a few years) single-node DataCenter, and another
single-node DataCenter (to act as disaster recovery)?
Thanks in advance for any suggestion or comment!
I'm sure there's a lots of pitfalls. A few of them in my mind right now:
* With a single node, you will completely lose the benefit of high
availability from Cassandra. Not only hardware failure will result
in downtime, routine maintenance (such as software upgrade) can also
3+ nodes per DC.
This is out of my usual experience with Cassandra and, as far as I read
around, out of most use-cases found on the website or this mailing list,
so the question is:
does it make sense to use Cassandra with a big (let's talk 6TB today, up
to 20TB in a few years) single-node Dat
> we had an awful performance/throughput experience with 3.x coming from 2.1.
> 3.11 is simply a memory hog, if you are using batch statements on the client
> side. If so, you are likely affected by
> https://issues.apache.org/jira/browse/CASSANDRA-16201
>
Confirming what Thomas writes, hea
From: Leon Zaruvinsky
Sent: Wednesday, October 28, 2020 5:21 AM
To: user@cassandra.apache.org
Subject: Re: GC pauses way up after single node Cassandra 2.2 -> 3.11 binary
upgrade
Our JVM options are unchanged between 2.2 and 3.11
For the sake of clarity, do you mean:
(a) you
> Our JVM options are unchanged between 2.2 and 3.11
>>
>
> For the sake of clarity, do you mean:
> (a) you're using the default JVM options in 3.11 and it's different to the
> options you had in 2.2?
> (b) you've copied the same JVM options you had in 2.2 to 3.11?
>
(b), which are the default opt
>
> Our JVM options are unchanged between 2.2 and 3.11
>
For the sake of clarity, do you mean:
(a) you're using the default JVM options in 3.11 and it's different to the
options you had in 2.2?
(b) you've copied the same JVM options you had in 2.2 to 3.11?
The distinction is important because at
Thanks Erick.
Our JVM options are unchanged between 2.2 and 3.11, and we have disk access
mode set to standard. Generally we’ve maintained all configuration between
the two versions.
Read throughput (rate, bytes read/range scanned, etc.) seems fairly
consistent before and after the upgrade ac
I haven't seen this specific behaviour in the past but things that I would
look at are:
- JVM options which differ between 3.11 defaults and what you have
configured in 2.2
- review your monitoring and check read throughput on the upgraded node
as compared to 2.2 nodes
- possibly no
On Wed, 28 Oct 2020 at 14:41, Rich Hawley wrote:
> unsubscribe
>
You need to email user-unsubscr...@cassandra.apache.org to unsubscribe from
the list. Cheers!
2TB data per node
> Heap Size: 12G / New Size: 5G
>
> I didn't even get very far in the upgrade - I just upgraded a binary of a
> single node to 3.11.6 (did not run upgradesstables) and let it sit. Within
> 10 minutes, I started seeing elevated GC pressure and lots of timeouts in
d a binary of a
single node to 3.11.6 (did not run upgradesstables) and let it sit. Within
10 minutes, I started seeing elevated GC pressure and lots of timeouts in
the metrics.
All three nodes, not just the upgraded one, are seeing GC problems.
GC par new time jumped from .38 up to 3%. CMS time
Hi,
I'm using ccm to create a cluster of 80 nodes on a physical server with 10
cores and 64GB of ram, but always the 43th node could not start with error:
java.lang.OutOfMemoryError: unable to create new native thread
apache cassandra 3.11.2
cassandra xmx600M
30GB of memory is still free
e tombstones make
it to all hosts before gc grace seconds expires
>
> But am I right about the following?
> In single-node Cassandra installations, it is irrelevant to run "nodetool
> repair" cron jobs.
It shouldnt be needed, because the tombstones must already be there.
O
Hello,
I think I understand why one needs to regularly run "nodetool repair" on
normal Cassandra installations with more than one node.
But am I right about the following?
In single-node Cassandra installations, it is irrelevant to run
"nodetool repair" cron jobs.
--
R
Hi ,
My Compression strategy in Production was *LZ4 Compression. *But I modified
it to Deflate
For compression change, we had to use *nodetool Upgradesstables *to
forcefully upgrade the compression strategy on all sstables
But once upgradesstabloes command completed on all the 5 nodes in the
c
quot;Kevin O'Connor"
> wrote:
> > This might be an interesting question - but is there a way to truncate
> data
> > from just a single node or two as a test instead of truncating from the
> > entire cluster? We have time series data we don't really care if we're
On 2017-07-11 20:09 (-0700), "Kevin O'Connor" wrote:
> This might be an interesting question - but is there a way to truncate data
> from just a single node or two as a test instead of truncating from the
> entire cluster? We have time series data we don't really
's
getting much more complicated.
Find some old SSTables for the table in question and delete them. Much
easier.
Patrick
On Tue, Jul 11, 2017 at 8:09 PM, Kevin O'Connor
wrote:
> This might be an interesting question - but is there a way to truncate
> data from just a single node o
This might be an interesting question - but is there a way to truncate data
from just a single node or two as a test instead of truncating from the
entire cluster? We have time series data we don't really care if we're
missing gaps in, but it's taking up a huge amount of space and w
On 2017-06-16 10:31 (-0700), John Hughes wrote:
> Hi Affan,
>
> Others can likely speak to this more authoritatively I am sure, but with a
> RF of 1x, I would not expect it to rebalance. Now if you were 4 nodes and a
> RF of 2x I would expect it to.
>
Even with an RF of 1, any token range th
XX.XX 24.39 GiB 256 49.8%
>>>>> fd92525d-edf2-4974-8bc5-a350a8831dfa 1a
>>>>> UN XX.XX.XX.XX 23.8 GiB 256 48.7%
>>>>> bdc597c0-718c-4ef6-b3ef-7785110a9923 1b
>>>>>
>>>>> Though maybe part of what you are experien
gt;>>>>>> Rack
>>>>>>> UN XX.XX.XX.XX22.71 GiB 256 47.6%
>>>>>>> 57dafdde-2f62-467c-a8ff-c91e712f89c9 1c
>>>>>>> UN XX.XX.XX.XX 17.17 GiB 256 51.3%
>>>>
1b
>>>>>> UN XX.XX.XX.XX 26.15 GiB 256 52.4%
>>>>>> acf5dd34-5b81-4e5b-b7be-85a7fccd8e1c 1c
>>>>>> UN XX.XX.XX.XX 16.64 GiB 256 50.2%
>>>>>> 6c8842dd-a966-467c-a7bc-bd6269ce3e7e 1a
>>>>>> UN XX.XX.XX.XX 2
c597c0-718c-4ef6-b3ef-7785110a9923 1b
>>>>>
>>>>> Though maybe part of what you are experiencing can be cleared up by
>>>>> repair/compaction/cleanup. Also, what are your outputs when you call out
>>>>> specific keyspaces? Do the numbers ge
what you are experiencing can be cleared up by
>>>> repair/compaction/cleanup. Also, what are your outputs when you call out
>>>> specific keyspaces? Do the numbers get more even?
>>>>
>>>> Cheers,
>>>>
>>>> On Mon, Jun 12, 2017 a
file.
>>>>
>>>> Akhil
>>>>
>>>> On Mon, Jun 12, 2017 at 6:18 PM, Junaid Nasir wrote:
>>>>
>>>>> No, I didn't set it (left it at default value)
>>>>>
>>>>> On Fri, Jun 9,
wrote:
>>>
>>>> No, I didn't set it (left it at default value)
>>>>
>>>> On Fri, Jun 9, 2017 at 3:18 AM, ZAIDI, ASAD A wrote:
>>>>
>>>>> Did you make sure auto_bootstrap property is indeed set to [true]
>>>>
property is indeed set to [true] when
>>>> you added the node?
>>>>
>>>>
>>>>
>>>> *From:* Junaid Nasir [mailto:jna...@an10.io]
>>>> *Sent:* Monday, June 05, 2017 6:29 AM
>>>> *To:* Akhil Mehra
>>>&
*Sent:* Monday, June 05, 2017 6:29 AM
>>> *To:* Akhil Mehra
>>> *Cc:* Vladimir Yudovin ; user@cassandra.apache.org
>>> *Subject:* Re: Convert single node C* to cluster (rebalancing problem)
>>>
>>>
>>>
>>
9 AM
>> *To:* Akhil Mehra
>> *Cc:* Vladimir Yudovin ; user@cassandra.apache.org
>> *Subject:* Re: Convert single node C* to cluster (rebalancing problem)
>>
>>
>>
>> not evenly, i have setup a new cluster with subset of data (around
une 05, 2017 6:29 AM
> *To:* Akhil Mehra
> *Cc:* Vladimir Yudovin ; user@cassandra.apache.org
> *Subject:* Re: Convert single node C* to cluster (rebalancing problem)
>
>
>
> not evenly, i have setup a new cluster with subset of data (around 5gb).
> using the configuration a
Did you make sure auto_bootstrap property is indeed set to [true] when you
added the node?
From: Junaid Nasir [mailto:jna...@an10.io]
Sent: Monday, June 05, 2017 6:29 AM
To: Akhil Mehra
Cc: Vladimir Yudovin ; user@cassandra.apache.org
Subject: Re: Convert single node C* to cluster (rebalancing
ode after tokens
>> changed.
>>
>> Best regards, Vladimir Yudovin,
>> *Winguzone <https://winguzone.com/?from=list> - Cloud Cassandra Hosting*
>>
>>
>> On Wed, 31 May 2017 03:55:54 -0400 *Junaid Nasir > >* wrote
>>
>> Cassan
d, 31 May 2017 03:55:54 -0400 Junaid Nasir <mailto:jna...@an10.io>> wrote
>
> Cassandra ensure that adding or removing nodes are very easy and that load is
> balanced between nodes when a change is made. but it's not working in my case.
> I have a sin
t; is balanced between nodes when a change is made. but it's not working in my
> case.
> I have a single node C* deployment (with 270 GB of data) and want to load
> balance the data on multiple nodes, I followed this guide
> <https://docs.datastax.com/en/cassandra/2.1/cassand
10.io>
wrote
Cassandra ensure that adding or removing nodes are very easy and that load is
balanced between nodes when a change is made. but it's not working in my case.
I have a single node C* deployment (with 270 GB of data) and want to load
balance the data on multiple nodes,
oken exist on both servers. other than that
> > nothing. if you need any more settings/details please ask. thank you for
> > your time
> >
> >
> > On Wed, May 31, 2017 at 2:04 PM, Oleksandr Shulgin
> > mailto:oleksandr.shul...@zalando.de>> wrote:
> > O
etails please ask. thank you
> for your time
> >
> >
> > On Wed, May 31, 2017 at 2:04 PM, Oleksandr Shulgin <
> oleksandr.shul...@zalando.de> wrote:
> > On Wed, May 31, 2017 at 9:55 AM, Junaid Nasir wrote:
> > Cassandra ensure that adding or removing nodes a
> On Wed, May 31, 2017 at 9:55 AM, Junaid Nasir wrote:
> Cassandra ensure that adding or removing nodes are very easy and that load is
> balanced between nodes when a change is made. but it's not working in my case.
> I have a single node C* deployment (with 270 GB of data) and wa
d, May 31, 2017 at 9:55 AM, Junaid Nasir wrote:
>>
>>> Cassandra ensure that adding or removing nodes are very easy and that
>>> load is balanced between nodes when a change is made. but it's not working
>>> in my case.
>>> I have a single node C* deploym
<
oleksandr.shul...@zalando.de> wrote:
> On Wed, May 31, 2017 at 9:55 AM, Junaid Nasir wrote:
>
>> Cassandra ensure that adding or removing nodes are very easy and that
>> load is balanced between nodes when a change is made. but it's not working
>> in my case.
>> I h
On Wed, May 31, 2017 at 9:55 AM, Junaid Nasir wrote:
> Cassandra ensure that adding or removing nodes are very easy and that load
> is balanced between nodes when a change is made. but it's not working in my
> case.
> I have a single node C* deployment (with 270 GB of data)
Cassandra ensure that adding or removing nodes are very easy and that load
is balanced between nodes when a change is made. but it's not working in my
case.
I have a single node C* deployment (with 270 GB of data) and want to load
balance the data on multiple nodes, I followed this guide
&
our own code/schema/table
>> will help highlight what the difference is that causes the problem.
>>
>> Doc:
>>
>> http://docs.datastax.com/en/latest-dse/datastax_enterprise/srch/srchTrnsFrm.html
>>
>> -- Jack Krupansky
>>
>> On Fri, Mar 18, 2016 at
Not that we aren't enthusiastic about you moving to Cassandra, but it needs
to be for the right reasons, and for Cassandra the right reasons are
scaling and HA.
In case it's not obvious, I would make a really lousy used-car or
real-estate/time-share salesman!
-- Jack Krupansky
On Thu, Apr 7, 201
On Wed, Apr 6, 2016 at 9:15 AM, Bhupendra Baraiya
wrote:
>
> The main reason we want to migrate to Cassandra is we have a denormalized
> data structure in Ms Sql server Database and we want to move to Open source
> database...
If it all boils down to this, then you might want to consider MySQL
tested that your
query model is correct
From: Bhupendra Baraiya [mailto:bhupendra.bara...@continuum.net]
Sent: woensdag 6 april 2016 16:15
To: user@cassandra.apache.org
Subject: RE: Cassandra Single Node Setup Questions
We have around 20 Million rows and around 200 concurrent users
The reason we
dra.apache.org
> *Subject:* RE: Cassandra Single Node Setup Questions
>
>
>
> We have around 20 Million rows and around 200 concurrent users
>
>
>
> The reason we want single Node is we have only single DC , I believe if
> there is only one DC there is no question of
When we start using cassandra in our company, we decide to use a single node
Cassandra cluster as PoC. Everything was correct until we really need the power
of a Cassandra cluster and then our data models were not appropriate for a
cluster with multiple nodes because of redundancy, data access
We have around 20 Million rows and around 200 concurrent users
The reason we want single Node is we have only single DC , I believe if there
is only one DC there is no question of keeping multiple nodes
The main reason we want to migrate to Cassandra is we have a denormalized data
structure in
applications which have a lot of data
and the need for high availability (redundancy, meaning at least three
copies of the data.) Neither of which seems to be your requirement.
How much data do you have? What led you to believe that you only need a
single node?
-- Jack Krupansky
On Wed, Apr 6
Hi ,
I had few question related to Single Node Setup in Cassandra
1) We want to install Cassandra but multiple Node is not what we need
Can we proceed with Single Node and store millions of data in Single
Node only
2) How many Partitions are allowed per Node , that is
highlight what the difference is that causes the problem.
Doc:
http://docs.datastax.com/en/latest-dse/datastax_enterprise/srch/srchTrnsFrm.html
-- Jack Krupansky
On Fri, Mar 18, 2016 at 4:30 AM, Joseph Tech wrote:
> Hi,
>
> I had setup a single-node DSE 4.8.x to start in Search mode t
Hi,
I had setup a single-node DSE 4.8.x to start in Search mode to explore some
aspects of Solr search with field transformers (FT). Even though the
configuration seems fine and Solr admin shows the indexed data, and
searches on the actual fields (stored=true) work fine, but the FTs are not
being
e
> will help highlight what the difference is that causes the problem.
>
> Doc:
>
> http://docs.datastax.com/en/latest-dse/datastax_enterprise/srch/srchTrnsFrm.html
>
> -- Jack Krupansky
>
> On Fri, Mar 18, 2016 at 4:30 AM, Joseph Tech
> wrote:
>
>> Hi,
>&
e is any documentation on migrating from a single
> node cassandra instance to a multinode cluster? My searches have been
> unsuccessful so far and I have had no luck playing with tools due to terse
> output from the tools.
>
> I currently use a single node having data that must be r
Hi,
I am wondering if there is any documentation on migrating from a single node
cassandra instance to a multinode cluster? My searches have been unsuccessful
so far and I have had no luck playing with tools due to terse output from the
tools.
I currently use a single node having data that
Hai Doan
>> Reply-To: "user@cassandra.apache.org"
>> Date: Saturday, January 30, 2016 at 3:54 AM
>> To: "user@cassandra.apache.org"
>> Subject: Re: Problem while migrating a single node cluster from 2.1 to
>> 3.2
>>
>> You need to upgra
urday, January 30, 2016 at 3:54 AM
> To: "user@cassandra.apache.org"
> Subject: Re: Problem while migrating a single node cluster from 2.1 to 3.2
>
> You need to upgrade first to C* 2.2 before migrating to C* 3.x
>
> For each version, read the NEWS.txt file and follow the proce
older versions is not supported.
From: DuyHai Doan
Reply-To: "user@cassandra.apache.org"
Date: Saturday, January 30, 2016 at 3:54 AM
To: "user@cassandra.apache.org"
Subject: Re: Problem while migrating a single node cluster from 2.1 to 3.2
You need to upgrade first to C* 2.2
ra-3.0/NEWS.txt
On Sat, Jan 30, 2016 at 8:10 AM, Ajaya Agrawal wrote:
> Hi,
>
> I am a newbie when it comes to Cassandra administration and operation. We
> have a single node cluster running 2.1 in EC2 and we are planning to move
> it to better single machine instance and want to r
Hi,
I am a newbie when it comes to Cassandra administration and operation. We
have a single node cluster running 2.1 in EC2 and we are planning to move
it to better single machine instance and want to run 3.2 on that.
I installed 3.2 on the new machine and created a snapshot of the old
cluster
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.
.
Other than durability, you single node cluster would be Single Point of Failure
for your site. RAID 5 will only protect you against a disk failure. But a
server may be down for other reasons too. Question is :Are you ok with site
going down?
I would suggest you to use hardware with smaller
durability, you single node cluster would be Single Point of Failure
for your site. RAID 5 will only protect you against a disk failure. But a
server may be down for other reasons too. Question is :Are you ok with site
going down?
I would suggest you to use hardware with smaller configuration to save
with a single node you have limited flexibility.
Just to be clear, Cassandra is still not recommended for "fat nodes" - even
if you can fit tons of data on the node, you may not have the computes to
satisfy throughput and latency requirements. And if you don't have enough
system memor
loss and you aren't
comparing apples to apples. Something like postgres is giving your durable
writes by default. Cassandra doesn't do that by default because you've
got redundant commit logs.
On Fri, Jan 22, 2016 at 1:48 PM Jack Krupansky
wrote:
> Is single-node Cassandra has the p
e ammo I need to shoot it down. I need
specific technical reasons.
Thanks!
--John
On Fri, Jan 22, 2016 at 4:47 PM, Jack Krupansky
wrote:
> Is single-node Cassandra has the performance (and capacity) you need and
> the NoSQL data model and API are sufficient for your app, and your dev
Is single-node Cassandra has the performance (and capacity) you need and
the NoSQL data model and API are sufficient for your app, and your dev and
ops and support teams are already familiar with and committed to Cassandra,
and you don't need HA or scaling, then it sounds like you are set.
er David Bauer Drive
Waterloo, ON, N2L 0A2, Canada
www.karoshealth.com
On Fri, Jan 22, 2016 at 4:32 PM, Jonathan Haddad wrote:
> If you're going to go with a bunch of smaller, single node servers, use
> Postgres. It's going to be more flexible with a smaller memory footprint.
> You c
If you're going to go with a bunch of smaller, single node servers, use
Postgres. It's going to be more flexible with a smaller memory footprint.
You could even use sqlite.
Would you run a single node zookeeper cluster? Single node map reduce?
Single node HDFS? I hope not.
C
Jeff, that may be true for many ... but for our application, the
performance of a single Cassandra node blows the doors off Oracle and
PostgreSQL.
On Fri, Jan 22, 2016 at 4:24 PM, Jeff Jirsa
wrote:
> The value of cassandra is in its replication – as a single node solution,
> it’s slow
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
necessarily recommend it but to answer John's question: my
understanding is that you want to keep it snappy and low-latency you should
watch out for GC pause and consider your GC tuning carefully, it being a
single node will cause the whole show to stop. Presumably your load won't
be very high.
A
with Single Node
To: user@cassandra.apache.org
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
aft
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'
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,
s
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
lume of data that needs migrating won’t be
>> huge, probably about 30G, but it is data that I definitely need to keep
>> (for historical analysis, audit etc).
>>
>>
>>
>> Thanks!
>>
>> Matthew
>>
>>
>>
>>
>>
>>
&g
ay 2015 14:38
> *To:* user@cassandra.apache.org
> *Subject:* Re: Start with single node, move to 3-node cluster
>
>
>
> will you add this lent one node into the 3N to form a cluster? but really
> , if you are just started, you could use this one node for your learning by
>
won’t be
huge, probably about 30G, but it is data that I definitely need to keep
(for historical analysis, audit etc).
Thanks!
Matthew
*From:* Jason Wee [mailto:peich...@gmail.com]
*Sent:* 26 May 2015 14:38
*To:* user@cassandra.apache.org
*Subject:* Re: Start with single node, move to 3
1 - 100 of 205 matches
Mail list logo
