Thanks for providing the links Erick, very helpful. Although it is slightly
inconvenient for me I now better understand the motivation.
On 10. Aug 2021, at 10:27, Erick Ramirez
mailto:erick.rami...@datastax.com>> wrote:
You are correct. Cassandra no longer allows invalid DC names for
Hi,
in Cassandra 3.11.x I was able to create key spaces with basically arbitrary
names for the data center. When I do this with Cassandra 4.0 I get a
"ConfigurationException: Unrecognized strategy option {}
passed to NetworkTopologyStrategy for keyspace ”.
This breaks some unit tests in our
Hi Erik,
thank you for the link, very instructive.
To summarise my understanding of your mail, the code and my experiments:
- as long as the compaction logger is running it will write into the same
“compaction.log" file
- if a new logger gets started (for example through restart of the
Hi,
Does anybody know the configuration for Extended Compaction Logging[1]? When is
a log rotation triggered and how many files are kept?
I did some googling, found [2] and checked the configuration in
/etc/cassandra/logback.xml, neither does mention anything about compaction
logging.
I am
e values, that's pretty small, and the overhead starts
showing up
On Tue, Dec 15, 2020 at 8:39 AM Jens Fischer
mailto:j.fisc...@sonnen.de>> wrote:
Hi Scott,
Thank you for your help. There was an error or at least an ambiguity in my
second Mail! I wrote:
I still see outgoing cr
ing to each DC2
and DC3. Once it gets written to DC2 node 1, it gets replicated locally to DC2
node 2; same for DC3 re DC3 node 2.
On Wed, Dec 2, 2020 at 9:36 AM Jens Fischer
mailto:j.fisc...@sonnen.de>> wrote:
Hi,
I checked for all the given other factors - anti entropy repair, hints, rea
to debug?
I define the "write size A” as follows: Take the incoming traffic from all
nodes inserting into DC1 and sum it up.
Best
Jens
On 30. Nov 2020, at 12:00, Jens Fischer
mailto:j.fisc...@sonnen.de>> wrote:
Hi Jeff,
Thank you for your answer, very helpful already!
All writ
width
I looked at all the Cassandra nodes in DC1 and the traffic coming from Node A.
I then summed up this traffic.
@Jeff: I assume this is closer to what you call “write size A”?
Best
Jens
On 26. Nov 2020, at 17:12, Jeff Jirsa
mailto:jji...@gmail.com>> wrote:
On Nov 26, 2020, at 9:
Hi,
we run a Cassandra cluster with three DCs. We noticed that the traffic incurred
by running the Cluster is significant.
Consider the following simplified IoT scenario:
* time series data from devices in the field is received at Node A
* Node A inserts the data into DC 1
* DC 1 replicates
plicas. So it makes a hint for that write and for that node. I am
not sure how is this related to turning off handoffs completely. I can do some
tests locally if time allows to investigate various scenarios. There might be
some subtle differences
On Wed, 3 Apr 2019 at 07:19, Jens F
Yes, Apache Cassandra 3.11.2 (no DSE).
On 2. Apr 2019, at 19:40, sankalp kohli
mailto:kohlisank...@gmail.com>> wrote:
Are you using OSS C*?
On Fri, Mar 29, 2019 at 1:49 AM Jens Fischer
mailto:j.fisc...@sonnen.de>> wrote:
Hi,
I have a Cassandra setup with multiple data centr
Hi,
I have a Cassandra setup with multiple data centres. The vast majority of
writes are LOCAL_ONE writes to data center DC-A. One node (lets call this node
A1) in DC-A has accumulated large amounts of hint files (~100 GB). In the logs
of this node I see lots of messages like the following:
12 matches
Mail list logo
