opened Pull Request #2861 on apache/cassandra
#2861 CASSANDRA-18956 Fix incorrect column identifier bytes problem when renaming a column
Replied to a message in 🌐Planet Cassandra in #🌐cassandra-chat
Check out the docs on Monitoring. There's a table-based metric called "TombstoneScannedHistogram" which should report on tombstones that have been returned from a query....
Check out the docs on Monitoring. There's a table-based metric called "TombstoneScannedHistogram" which should report on tombstones that have been returned from a query. https://cassandra.apache.org/doc/3.11/cassandra/operating/metrics.html#table-metrics
opened Pull Request #2860 on apache/cassandra
#2860 CASSANDRA-18996 Add documentation about crypto providers
opened Pull Request #2859 on apache/cassandra
#2859 CASSANDRA-18995 Improve documentation for snitches
Mentioned @cassandra
On my honor, I promise that I will do my best to do my duty to my own bag, and to farm #MEMEPOINTS at all times.
It ain’t much, but it’s honest work. 🧑
Mentioned @cassandra
On my honor, I promise that I will do my best to do my duty to my own bag, and to farm #MEMEPOINTS at all times.
It ain’t much, but it’s honest work. 🧑
commented Pull Request #2845 on apache/cassandra
Thanks @Maxwell-Guo for spotting those! I am pushing a new commit to update and will check the other PRs too.
opened Pull Request #2858 on apache/cassandra
#2858 CASSANDRA-18960 trunk: Upgrade Python driver to 3.28.0
opened Pull Request #2857 on apache/cassandra
#2857 CASSANDRA-18960 5.0: Upgrade Python driver to 3.28.0
commented Pull Request #170 on apache/cassandra-website
Same notes as @michaelsembwever , except:
and… of curiosity… given the versioning differences in the doc, wouldn't this be better moved in-tree ? (easier to read, easier to maintain) It is better if the instruction is in...
Same notes as @michaelsembwever , except:
and… of curiosity… given the versioning differences in the doc, wouldn't this be better moved in-tree ? (easier to read, easier to maintain) It is better if the instruction is in one place. Otherwise, people will be merging, breaking, and searching for more instructions... Keeping it in one place makes it easier. On the other hand, if we decide to split - this should be done in another ticket. This one is almost ready, and it has been reviewed three times already.
opened Pull Request #2856 on apache/cassandra
#2856 CASSANDRA-18912 5.0 change "since" in Deprecated annotation for Version.hasAccurateMinMax…
Mentioned @cassandra
I'm using datastax cassandra in my graduate work and I want to get this metric but I can't find any documentation about it. I am using python connector. Is it possible to get this information about each query executed? If yes, how can I get...
I'm using datastax cassandra in my graduate work and I want to get this metric but I can't find any documentation about it. I am using python connector. Is it possible to get this information about each query executed? If yes, how can I get it?
opened Pull Request #2855 on apache/cassandra
#2855 CASSANDRA-18992 Exclude the jna transitive dependency from ohc-core
opened Pull Request #2854 on apache/cassandra
#2854 CASSANDRA-18992 Exclude the jna transitive dependency from ohc-core
I've been looking for a solution and neither of them could solve the issue.
I can't connect to Cassandra container with DataStax C# Cassandra driver, getting the error:
Unhandled exception....
I've been looking for a solution and neither of them could solve the issue.
I can't connect to Cassandra container with DataStax C# Cassandra driver, getting the error:
Unhandled exception. Cassandra.NoHostAvailableException: All hosts tried for query failed (tried 127.0.0.1:9042: SocketException 'Connection refused')
When I run the ASP.NET application locally, the connection to the Cassandra container is successful. But when I run docker compose to run Cassandra container and my ASP.NET Service container to communicate together, the ASP.NET container fails to connect. Am I missing something?
ASP.NET code:
var cluster = Cluster.Builder()
.AddContactPoints("127.0.0.1")
.WithQueryOptions(queryOptions)
.WithDefaultKeyspace("chathistory")
.Build();
var session = cluster.ConnectAndCreateDefaultKeyspaceIfNotExists();
Docker compose
version: "3.8"
services:
chat-server:
build:
context: ./ChatServer
dockerfile: Dockerfile
environment:
- ASPNETCORE_ENVIRONMENT=Development
ports:
- 5134:5134
depends_on:
- chat-cassandra
chat-cassandra:
image: cassandra:3.1
container_name: chat-cassandra
ports:
- 9042:9042
restart: always
volumes:
- ./cassandra_data:/var/lib/cassandra
commented Pull Request #75 on apache/cassandra-sidecar
closing since the patch has been merged.
we use cassandra 3.11, now had a 7 nodes cluster. now we join a new node(172.19.19.33) into this. in system.log,we got those messages:
ERROR StreamSession.java:593 [Stream #xxxx] Streaming error occured on session with peer 172.19.19.12...
we use cassandra 3.11, now had a 7 nodes cluster. now we join a new node(172.19.19.33) into this. in system.log,we got those messages:
ERROR StreamSession.java:593 [Stream #xxxx] Streaming error occured on session with peer 172.19.19.12 java.lang.NullPointerException: null at org.apache.cassandra.db.lifecycle.LifecycleTransaction.update(LifecycleTransaction.java:340) xxxxx xxxx at ort.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:317)
then we join once more, and use tcpdump catch the pacakges from 172.19.19.12 and this node, we found when 172.19.19.12 send a TCP ZeroWindow to 172.19.19.19.33 and then send TCP Flag RST right away。
how do we do for this. what can i do for join a new node into this cluster.
I do set linux tcp_rmem and use nodetool setstreamthrougput 32 and nodetool setinterdcstreamthrougput 32 for other nodes exclude 172.19.19.33. These methods does not fix this problem. Then we create a new cluster, insert about 1TB data, then join new node to this cluster. It look like normal and work good.
The 172.19.19.12 cluster had some problems before, at 70's day before, the cluster Schema vesionss had changed by one of the cluster's node restart, then we found the table was not created in all nodes, so we got the table data file and place it into seed's nodes (one of them),then the cluster become normal.