Over the past year we've migrated several clusters from DSE to Apache
Cassandra. We've mostly done I place conversions node by node with no
downtime. DSE 4.8.X to Apache Cassandra 2.1.x
On Wed, May 29, 2019 at 8:55 PM Goetz, Anthony
wrote:
> My team migrated from DSE to OSS a few years ago by
ause it
> may not impact you but may represent a real bug.
>
> Would be great if you could turn on tracing.
>
>
>
> On Wed, Oct 16, 2019 at 12:17 PM Patrick Lee
> wrote:
>
>> we do have otc_coalescing_strategy, we did run into that long while back
>> wer
<https://issues.apache.org/jira/browse/CASSANDRA-12676> since you’ve
> upgraded from 2.x? also if you found luck by increasing
> native_transport_max_threads to address blocked NTRs (CASSANDRA-11363)?
>
> ~Asad
>
>
>
>
>
>
>
> *From:* Patrick Lee [mailto:patrickclee0...@gma
t;
> ---
> Alain Rodriguez - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> Le ven. 4 oct. 2019 à 00:25, Patrick Lee a
> écrit :
>
>> this table was actually l
I have a cluster that is running 3.11.4 ( was upgraded a while back from
2.1.16 ). what I see is a steady rate of read repair which is about 10%
constantly on only this 1 table. Repairs have been run (actually several
times). The table does not have a lot of writes to it so after repair, or
this table was actually leveled compaction before, just changed it to size
tiered yesterday while researching this.
On Thu, Oct 3, 2019 at 4:31 PM Patrick Lee
wrote:
> its not really time series data. and it's not updated very often, it
> would have some updates but pretty infr
data? If so, I have run into issues with repair on
> time series data using the SizeTieredCompactionStrategy. I have had
> better luck using the TimeWindowCompactionStrategy.
>
>
>
> John
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> fo
I've actually noticed this as well on a few clusters I deal with but after
upgrading Cassandra from 3.11 to 4 we also changed to use Java 11 shortly
after the cluster upgrade. After I moved to Java 11 I have not experienced
a problem.
On Wed, Aug 16, 2023 at 12:12 PM vaibhav khedkar
wrote:
>
time given the size of our infrastructure. Is it safe to assume that the issue exists in the combination of upgrades from 3.11.x to 4.0.x and running on JAVA 8 ? Did you happen to have created a ticket for this when you observed the issue ? Thanks vaibhavOn Wed, Aug 16, 2023 at 11:15 AM Patrick Lee
