1500 is probably fine
3000 is probably fine
One place you may see issues is on reconnect during a bounce - make sure you
have your auth caches enabled and consider dropping the bcrypt rounds (defaults
to 2^10, which takes some non-trivial cpu to hash the password supplied on each
new connectio
By retry logic, I’m going to guess you are doing some kind of version
consistency trick where you have a non-key column managing a visibility horizon
to simulate a transaction, and you poll for a horizon value >= some threshold
that the app is keeping aware of.
Note that these assorted variatio
I think I recall seeing you post the same question on ASF Slack yesterday.
I haven't used Debezium so I can't comment on it. But are you looking for
something to consume the CDC logs? If so, you might be interested in the
DataStax CDC Kafka connector that offers bi-directional data movement.
For
I have found some project that support parse Commitlog (CDC), such as :
https://github.com/rustyrazorblade/commitlog-viz this seems wrote by Jon
Haddad , but is not work yet. and commitlog extract tool :
https://github.com/carloscm/cassandra-commitlog-extract but it also do some
output to other
This isn't expected at all and there's definitely something wrong.
However, when I restart last node (others remain down), when it comes up
> "nodetool status" shows all down nodes under "DC1" no matter how long I
> wait.
>
This sounds like the node can't gossip with other nodes. My hypothesis is
There’s two problems with this approach if you need strict correctness
1) after you delete the sstable and before you repair you’ll violate
consistency, so you’ll potentially serve incorrect data for a while
2) The sstable May have a tombstone past gc grace that’s shadowing data in
another sst
Stop the node
Delete as per option 2
Run repair
Regards,
Nitan
Cell: 510 449 9629
> On May 26, 2020, at 6:46 PM, Leon Zaruvinsky wrote:
>
>
> Hi all,
>
> I'm looking to understand Cassandra's behavior in an sstable corruption
> scenario, and what the minimum amount of work is that needs t
Hi all,
I'm looking to understand Cassandra's behavior in an sstable corruption
scenario, and what the minimum amount of work is that needs to be done to
remove a bad sstable file.
Consider: 3 node, RF 3 cluster, reads/writes at quorum
SStable corruption exception on one node at
keyspace1/table1/
Thank you for the response. Will follow the recommendation for the update. So
with Read=LOCAL_QUORUM we should see some latency, but not failures during RF
change right?
We do mitigate the issue of not seeing writes when set to Local_one, by having
a Retry logic in the app
___
Hello,
Our service code is written in goland uses gocql to connect todb and we
have 30 node cluster. And we have service connections coming from
kubernettes pods when we scaleup pods to 500 for each pod we are getting
connections 1500 per each node. We are not seeing any issues now but wanted
to
Hi guys,
I'm looking for a tool that helps me to parse CommitLog (CDC).
I found Debezium https://debezium.io/documentation/reference/1.2/ and I
want to know if someone has used it or if you could advise me other
solutions?
Cheers.
11 matches
Mail list logo
