cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Hancock <>
Subject Re: compaction_throughput_mb_per_sec
Date Tue, 05 Jan 2016 19:34:29 GMT
Will do.  I searched the doc for additional usage of the term "system"

commitlog_segment_size_in_mb refers to "every table in the system"
concurrent_writes talks about CPU cores "in your system"

That's it for "system" other than the compaction_throughput_mb_per_sec
which refers to "across the entire system".

node is the predominant term in the yaml configuration, though I can
certainly see potential confusion with vnodes.

On Tue, Jan 5, 2016 at 2:26 PM, Robert Coli <> wrote:

> On Tue, Jan 5, 2016 at 6:50 AM, Ken Hancock <>
> wrote:
>> As to why I think it's cluster-wide, here's what the documentation says:
> Do you see "system" used in place of "cluster" anywhere else in the docs?
> I think you are correct that the docs should standardize on "system"
> instead of "node", because node to me includes vnodes. "system" or "host"
> is what I think of as "the entire cassandra process".
> If I were you, I'd email docs AT datastaxdotcom with your feedback. :D
> =Rob

*Ken Hancock *| System Architect, Advanced Advertising
SeaChange International
50 Nagog Park
Acton, Massachusetts 01720 | | NASDAQ:SEAC
Office: +1 (978) 889-3329 | [image: Google Talk:] | [image:
Skype:]hancockks | [image: Yahoo IM:]hancockks[image: LinkedIn]

[image: SeaChange International]
<>This e-mail and any attachments may contain
information which is SeaChange International confidential. The information
enclosed is intended only for the addressees herein and may not be copied
or forwarded without permission from SeaChange International.

View raw message