opened Pull Request #254 on apache/cassandra-dtest
#254 Fix timeouts in pytest.ini to not take preference over test decorations
opened Pull Request #3128 on apache/cassandra
#3128 CASSANDRA-19422 5.0 fix scm url links
opened Pull Request #3127 on apache/cassandra
#3127 CASSANDRA-19422 3.11 fix scm url links
opened Pull Request #3126 on apache/cassandra
#3126 CASSANDRA-19422 3.0 fix SCM url links
opened Pull Request #3125 on apache/cassandra
#3125 CASSANDRA-19422 trunk fix scm url links
opened Pull Request #3124 on apache/cassandra
#3124 CASSANDRA-19422 4.0 fix scm url links
opened Pull Request #3123 on apache/cassandra
#3123 CASSANDRA-19422 4.1 fix scm url links
You cannot perform joins in Cassandra. If you have designed a data model and find that you need something like a join, you’ll have to either do the work on the client side, or create a denormalized second table that represents the join results...
You cannot perform joins in Cassandra. If you have designed a data model and find that you need something like a join, you’ll have to either do the work on the client side, or create a denormalized second table that represents the join results for you.
Reference Link https://cassandra.apache.org/doc/stable/cassandra/data_modeling/data_modeling_rdbms.html#:~:text=No%20joins,the%20join%20results%20for%20you.
While i was working with a project (a playground project with nodeJS) I found that there is no joining option in the cassandra-nodejs ORM. Is there any option to have this in any ORM in built (except raw query).
I tried lots of...
While i was working with a project (a playground project with nodeJS) I found that there is no joining option in the cassandra-nodejs ORM. Is there any option to have this in any ORM in built (except raw query).
I tried lots of tutorials and Node Library search but not found a suitable solutions.
commented Pull Request #3121 on apache/cassandra
Review comments added and new workflow example here
Current tooling doesn't support removal of a workflow so I couldn't remove the 'separate' ones. I cleaned them though.
Apologies I just realized I used the wrong base branch name in this PR.
opened Pull Request #267 on apache/cassandra-website
#267 CASSANDRA-19423: WESBITE - Catalysts and community page updates
opened Pull Request #3122 on apache/cassandra
#3122 CASSANDRA-18940 Record latencies for SAI post-filtering reads against local storage
Not very sure about the above, but I've almost always leverage GossipingPropertyFileSnitch these days over any other options. The GossipingPropertyFileSnitch represents a significant advancement in how Cassandra...
Not very sure about the above, but I've almost always leverage GossipingPropertyFileSnitch these days over any other options. The GossipingPropertyFileSnitch represents a significant advancement in how Cassandra handles network topology, offering dynamic, efficient, and fault-tolerant data placement and request routing. Its integration with the gossip protocol and support for dynamic updates without cluster restarts make it a preferred choice for production Cassandra deployments, especially those spanning multiple datacenters.
Points to remember:
- By design, the
GossipingPropertyFileSnitchfalls back on thePropertyFileSnitch's apachecassandra-topology.propertiesas a means to allow clusters to be migrated toGossipingPropertyFileSnitch. - If the cluster is already on
GossipingPropertyFileSnitch, ensure that apachecassandra-topology.propertieshas been removed or does not exist even if there are no issues with the nodes to ensure the cluster does not encounter problems in the future. More at CASSANDRA-11508 - FYI, CASSANDRA-10745 is a proposal to deprecate and fully remove the PropertyFileSnitch in future releases.
I needed to convert a gpg key for Cassandra. I downloaded it wget https://downloads.apache.org/cassandra/KEYS
If you want to convert with the command: iconv -f utf-8 -t...
I needed to convert a gpg key for Cassandra. I downloaded it wget https://downloads.apache.org/cassandra/KEYS
If you want to convert with the command: iconv -f utf-8 -t us-ascii//TRANSLIT KEYS > KEYS_ascii I received the following output: iconv: illegal input sequence at position 169653
After removing the lines containing invalid characters from the file (the last one in the name Rene): sed -i '/E0B7D6BE/d' KEYS I was able to successfully convert the file as needed
Can I ask you to correct the file, please? https://downloads.apache.org/cassandra/KEYS So that it doesn't contain any wrong characters?
Regards. Robert
opened Pull Request #253 on apache/cassandra-dtest
#253 Test Failure: dtest-upgrade.upgrade_tests.upgrade_through_versions_te…
commented Pull Request #3120 on apache/cassandra
hi @JackPGreen , every change needs a corresponding JIRA issue. I created it here (1). Feel free to step in and drive this otherwise I will do.
I was looking into Cassandra dynamic snitch. Suppose there are 3 replica nodes (N1, N2 and N3) for a particular keyspace. Suppose, for now the snitch considers only latency for score calculation. Let for a particular instance,
N1 =...
I was looking into Cassandra dynamic snitch. Suppose there are 3 replica nodes (N1, N2 and N3) for a particular keyspace. Suppose, for now the snitch considers only latency for score calculation. Let for a particular instance,
N1 = 1ms,
N2=2ms,
N3=3ms (due to some network error).
Let for a session, if read consistency = 2, coordinator will choose N1 for full data request and N2 for digest request.
- Will the coordinator completely ignore N3 for this session or perform digest request and read repair on it too in background (asynchronously)?
Also I have problem understanding the need of dynamic_snitch_reset_interval_in_ms in the first place. Since the latencies of every node must have been collected and score calculated every dynamic_snitch_update_interval_in_ms interval. If network error is resolved and node N3’s latency decreases to 0.5ms, the snitch changes the preferred node itself. Is it only to cater that 10% latency improvement (since dynamic snitch changes the preferred node if current node performs 10% less than highest performing node)?
- Why is dynamic_snitch_reset_interval_in_ms required ?
I am assuming that score of every node is calculated even if coordinator ignores N3 for current session (which I am not sure) because another session might have RC of 3 in which case coordinator must consider node N3 too.
Am I missing something ? This is really confusing to me.
Replied to thread: Consistent issues joining nodes in 4.1.3 in 🌐Planet Cassandra in #🌐cassandra-chat
Bah, fixed in 5.0 apparently: https://issues.apache.org/jira/browse/CASSANDRA-17754
Fix Version/s 5.0-alpha1 [ 12353513 ]
Replied to thread: Consistent issues joining nodes in 4.1.3 in 🌐Planet Cassandra in #🌐cassandra-chat
oh, describe keyspace is CREATE KEYSPACE system_auth WITH replication = {'class': 'NetworkTopologyStrategy', 'gcp.us-west1': '3', 'gcp.us-east4': '3'} AND durable_writes = true;
Replied to thread: Consistent issues joining nodes in 4.1.3 in 🌐Planet Cassandra in #🌐cassandra-chat
well, usually fixes it. if not, then I have to nuke it and rejoin
Replied to thread: Consistent issues joining nodes in 4.1.3 in 🌐Planet Cassandra in #🌐cassandra-chat
I am having a consistent issues with multi-dc cluster when joining other nodes. After it gets to this point during the bootstrap it stalls in an infinite loop. Shows as UJ as expected. Restarting the node after the initial...
I am having a consistent issues with multi-dc cluster when joining other nodes. After it gets to this point during the bootstrap it stalls in an infinite loop. Shows as UJ as expected. Restarting the node after the initial bootstrap hangs like this "Fixes" it and brings to to UN. Obvously I have to run repair, but I'm not sure what is causing this. Are my system keyspaces not correct or something ?
Feb 22 01:53:25 cassandra-use4-13 docker[384955]: INFO [OptionalTasks:1] 2024-02-22 01:53:25,736 NoSpamLogger.java:105 - "Cannot read from a bootstrapping node" while executing SELECT * FROM system_auth.roles WHERE role = 'cassandra' ALLOW FILTERING
Feb 22 01:53:25 cassandra-use4-13 docker[384955]: WARN [OptionalTasks:1] 2024-02-22 01:53:25,736 CassandraRoleManager.java:359 - CassandraRoleManager skipped default role setup: some nodes were not ready
Feb 22 01:53:25 cassandra-use4-13 docker[384955]: INFO [OptionalTasks:1] 2024-02-22 01:53:25,736 CassandraRoleManager.java:395 - Setup task failed with error, rescheduling
Feb 22 01:53:35 cassandra-use4-13 docker[384955]: WARN [OptionalTasks:1] 2024-02-22 01:53:35,737 CassandraRoleManager.java:359 - CassandraRoleManager skipped default role setup: some nodes were not ready
Feb 22 01:53:35 cassandra-use4-13 docker[384955]: INFO [OptionalTasks:1] 2024-02-22 01:53:35,737 CassandraRoleManager.java:395 - Setup task failed with error, rescheduling
Feb 22 01:53:45 cassandra-use4-13 docker[384955]: WARN [OptionalTasks:1] 2024-02-22 01:53:45,738 CassandraRoleManager.java:359 - CassandraRoleManager skipped default role setup: some nodes were not ready
Feb 22 01:53:45 cassandra-use4-13 docker[384955]: INFO [OptionalTasks:1] 2024-02-22 01:53:45,738 CassandraRoleManager.java:395 - Setup task failed with error, rescheduling
opened Pull Request #266 on apache/cassandra-website
#266 CASSANDRA-19420 Link fix for mathematical functions on 5.0 landing page