opened Pull Request #2778 on apache/cassandra
#2778 Wait for live endpoints as part of waiting for gossip to settle
After install Cassandra by ansible in DebianOS, here is my /var/log/:
$ ls -ll /var/log/
''' total 636 drwxr-xr-x 5 root root 320 Oct 6 09:33 .
drwxr-xr-x 11 root root 4096 Oct 1 01:08 ..
...After install Cassandra by ansible in DebianOS, here is my /var/log/:
$ ls -ll /var/log/
''' total 636 drwxr-xr-x 5 root root 320 Oct 6 09:33 .
drwxr-xr-x 11 root root 4096 Oct 1 01:08 ..
drwxr-xr-x 2 root root 100 Oct 6 09:48 apt
-rw-r----- 1 root adm 54315 Oct 6 09:52 auth.log
-rw-rw---- 1 root utmp 0 Oct 6 01:07 btmp
drwx------ 2 cassandra cassandra 240 Oct 6 09:48 cassandra <==========HERE========
-rw-r----- 1 root adm 148418 Oct 6 09:52 daemon.log
-rw-r----- 1 root adm 964 Oct 6 01:07 debug
-rw-r--r-- 1 root root 3532 Oct 6 09:48 dpkg.log
-rw-r----- 1 root adm 34575 Oct 6 01:07 kern.log
-rw-rw-r-- 1 root utmp 296296 Oct 6 09:50 lastlog
-rw-r----- 1 root adm 63877 Oct 6 09:48 messages
drwx------ 2 root root 40 Oct 6 01:07 private
-rw-r----- 1 root adm 214245 Oct 6 09:52 syslog
-rw-r----- 1 root adm 30504 Oct 6 09:48 user.log
-rw-rw-r-- 1 root utmp 70000 Oct 6 09:50 wtmp
'''
This time, after installation Cassandra cluster is up and running. But after REBOOT /var/log/cassandra not available and cassandra have no permission to mkdir in/var/log and failed to start.
$ ls -ll /var/log/
''' total 352 -rw-r----- 1 root adm 1167 Oct 6 09:51 auth.log
-rw-rw---- 1 root utmp 0 Oct 6 09:50 btmp
-rw-r----- 1 root adm 114270 Oct 6 09:56 daemon.log
-rw-r----- 1 root adm 964 Oct 6 09:50 debug
drwxr-x--- 2 influxdb influxdb 40 Oct 6 09:50 influxdb
-rw-r----- 1 root adm 34619 Oct 6 09:50 kern.log
-rw-rw-r-- 1 root utmp 296296 Oct 6 09:50 lastlog
-rw-r----- 1 root adm 35237 Oct 6 09:51 messages
drwx------ 2 root root 40 Oct 6 09:50 private
-rw-r----- 1 root adm 151361 Oct 6 09:56 syslog
-rw-r----- 1 root adm 1820 Oct 6 09:51 user.log
-rw-rw-r-- 1 root utmp 2400 Oct 6 09:50 wtmp
'''
$ nodetool status mkdir: cannot create directory '/var/log/cassandra': Permission denied nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused (Connection refused)'.
I've tried so many times, but don't know why system deleted my cassandra log dir.
- try reinstall Cassandra [DIDNT WORK]
- create a service mkdir /var/log/cassandra at reboot time [DINDT WORK]
Please help me.
opened Pull Request #2777 on apache/cassandra
#2777 Enable Direct-IO feature for CommitLog files using Java native API's.
I have two dc cluster, where one dc was upgraded from Cassandra 2.2.19 to 3.11.13. Currently I notice cql timeout reported after the upgrade on the Cassandra 3.x DC. The other dc which is on version 2.x does not have this issue. Could you...
I have two dc cluster, where one dc was upgraded from Cassandra 2.2.19 to 3.11.13. Currently I notice cql timeout reported after the upgrade on the Cassandra 3.x DC. The other dc which is on version 2.x does not have this issue. Could you please let me know if Cassandra 3.11.13 version needs timeout value to be increased than the previous setting ? Below are the current timeout values configured, what must be done in order to resolve this issue?
Error:
ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting for replica nodes' responses] message="Operation timed out - received only 3 responses." info={'received_responses': 3, 'required_responses': 4, 'consistency': 'QUORUM'}
Timeout value in Casssandra.yaml Configuration file:
read_request_timeout_in_ms: 5000 range_request_timeout_in_ms: 10000 write_request_timeout_in_ms: 10000 counter_write_request_timeout_in_ms: 5000 cas_contention_timeout_in_ms: 1000 truncate_request_timeout_in_ms: 60000 request_timeout_in_ms: 10000 cross_node_timeout: false
opened Pull Request #2776 on apache/cassandra
#2776 [DO NOT MERGE] C-18798 ListType and Accord
opened Pull Request #2775 on apache/cassandra
#2775 CASSANDRA-18907 Remove unnecessary reporter-config3 dependency
Pull Request #235 on apache/cassandra-dtest merged by jacek-lewandowski
#235 Fix secondary_indexes_test.py
Replied to a message in 🌐Planet Cassandra in #🌐cassandra-chat
is there any information on whether it noticeably affects the compaction process
commented Pull Request #2773 on apache/cassandra
Can you add the CI link please?
opened Pull Request #2774 on apache/cassandra
#2774 CASSANDRA-18889 trunk: Fix vector type to support DDM's mask_default function
We deploy our cassandra node using helm cass-operator-0.42.0 and we encountered terminated instana-cassandra-default-sts-2 from cluster upgrade due to cassandra node changed.
NAME READY STATUS ...We deploy our cassandra node using helm cass-operator-0.42.0 and we encountered terminated instana-cassandra-default-sts-2 from cluster upgrade due to cassandra node changed.
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
cass-operator-578f797bcf-fdtlx 1/1 Running 0 5d15h <none> <none>
instana-cassandra-default-sts-0 2/2 Running 0 14d <none> <none>
instana-cassandra-default-sts-1 2/2 Running 0 5d15h <none> <none>
instana-cassandra-default-sts-2 1/2 Running 0 5d14h 10.XXX.10.132 <none> <none>
Error:
URGENT_MESSAGES-[no-channel] dropping message of type ECHO_REQ whose timeout expired before reaching the network
INFO [Messaging-EventLoop-3-3] 2023-09-28 15:29:25,824 NoSpamLogger.java:92 - /10.254.20.138:7000->/10.254.12.178:7000-URGENT_MESSAGES-[no-channel] failed to connect
io.netty.channel.ConnectTimeoutException: connection timed out: /10.254.12.178:7000
Question: IP 10.254.12.178 no longer used and assigned. It could be the old IP assigned to terminated instana-cassandra-default-sts-2. The new restarted statefulset have new ip assigned 10.xxx.10.132. But Sassandra cluster still circulated and broadcast the message to old IP.
How to recovered in this case for cass-operator version cass-operator-0.42.0.
In Cassandra 3.11v, we set read-timeout-millis properties like below.
spring:
data:
cassandra:
read-timeout-millis: 2000ms
But how can we set read-timeout...
In Cassandra 3.11v, we set read-timeout-millis properties like below.
spring:
data:
cassandra:
read-timeout-millis: 2000ms
But how can we set read-timeout properties in the latest Cassandra DataStax 4.x(4.13)?
As per the properties reference given by Cassandra DataStax, we don't find read-timeout https://docs.datastax.com/en/developer/java-driver/4.13/manual/core/configuration/reference/
How can we set read-timeout properties in the latest Cassandra DataStax 4.x?
Replied to thread: I received this message Anyone from in 🌐Planet Cassandra in #🌐cassandra-chat
We have to keep up with all this to keep our security compliance for things like PCI
Replied to thread: I received this message Anyone from in 🌐Planet Cassandra in #🌐cassandra-chat
@patrick_mcfadin I can take the trainign too 🙂 , even though I am not DataStax - these security trainings are good stuff most of the time