I have observed a memory leak in 3.11.2 version similar situation which
Bobbie has mentioned, We faced corrupt sstable issue after disk space was
100% full (due to snapshots) in multiple nodes (we have default
disk_failure_policy)
After clearing the snapshots we ran repair and observed following i
The drivers are not maintained by the Cassandra project, it's up to each
driver maintainer to list their compatibility.
On Tue, Jan 22, 2019 at 10:48 AM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Thanks for the response Amanda,
>
> Yes we can go with the latest version but we are
Thanks for the response Amanda,
Yes we can go with the latest version but we are trying one change at a
time, so want to make sure the version compatibility. b/w any plans to
update the documentation for the latest versions for apache cassandra?
On Tue, Jan 22, 2019 at 10:28 AM Amanda Moran
wrot
Hi there-
I checked with the team here (at DataStax) and this should work. Any reason
you need to stick with Java Driver 3.2, there is a 3.6 release.
Thanks!
Amanda
On Tue, Jan 22, 2019 at 8:45 AM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Hello,
>
> I am looking for Datastax
Thanks a lot Chris.
On Tue, Jan 22, 2019 at 11:08 AM Chris Lohfink
wrote:
> In 3.x+ the format on disk is the same with compact storage on or off so
> you shouldn't expect much of a difference in table size with the new
> storage format compared to compact vs non compact in 2.x.
>
> Chris
>
> On
In 3.x+ the format on disk is the same with compact storage on or off so you
shouldn't expect much of a difference in table size with the new storage format
compared to compact vs non compact in 2.x.
Chris
> On Jan 22, 2019, at 10:21 AM, Nitan Kainth wrote:
>
> hey Chris,
>
> We upgraded for
Hello,
I am looking for Datastax Driver compatibility vs apache cassandra 3.11.3
version.
However the doc doesn't talk about the 3.11 version.
https://docs.datastax.com/en/driver-matrix/doc/driver_matrix/javaDrivers.html
Can someone please confirm if the Datastax Java Driver 3.2.0 version work
wi
hey Chris,
We upgraded form 3.0.4 to 3.11. yes, I did run upgradesstables -a to
migrate sstables.
Here is the table structure:
CREATE TABLE ks.cf1 ( key text, column1 timestamp, value blob, PRIMARY KEY
(key, column1) ) WITH COMPACT STORAGE CREATE TABLE ks.cf2 ( key bigint,
column1 text, value blo
What version are you running? Did you include an upgradesstables -a or
something to rebuild without the compact storage in your migration?
After 3.0 the new format can be more or less the same size as the 2.x compact
storage tables depending on schema (which can impact things a lot).
Chris
> O
Hi,
We are testing to migrate off from compact storage. After removing compact
storage, we were hoping to see an increase in disk usage but nothing
changed.
any feedback, why didn't we see an increase in storage?
Hi Thomas,
I misread the question. The metrics indicated here are dropped due to
dropped messages.
The value you see in the log is dynamically generated so unfortunately the
metrics you are looking for is not available through JMX.
However, the Cassandra logs the value in system.peer_events tabl
Hi,
thanks. I have seen that, but I’m not sure if this maps 1:1 to dropped hints in
the Cassandra log.
Dropped “message” could also mean that something went wrong during a hint
replay for a recovering node, but not necessarily dropped hints due to a node
being offline longer than the default 3
Hello Alain ,
Good Morning & thank you for these details , very interesting your calcul
for the node and vnodes
thanks for your example for calculate the tokens in the cluster and i
gonna read & take my class of maths for understand the formule and document
of mr Joey Lynch i thin so very intere
Hi Thomas,
The dropped hints count and various rates are available in the following
location:
org.apache.cassandra.metrics:type=DroppedMessage,scope=HINT,name=Dropped,*
org.apache.cassandra.metrics/DroppedMessage/HINT/Attributes/Count
org.apache.cassandra.metrics/DroppedMessage/HINT/Attributes
14 matches
Mail list logo
