Hi
For us, clearly the willing to improve (and not give up) materialized views
with a quality testing follow up
https://issues.apache.org/jira/browse/CASSANDRA-15921
Materialized view is a fantastic tool very useful for us.
Our use case is to deduplicate and order : We want to store the last
+1 for Jon K's comment!
On Sun, May 9, 2021 at 9:14 PM Jonathan Koppenhofer
wrote:
> I addition to Jeff's answer... Certificate hot reloading... For an
> organization that uses annual certs :)
>
>
> On Fri, May 7, 2021, 8:47 AM Durity, Sean R
> wrote:
>
>> There is not enough 4.0 chatter here.
Is there a good place to see the docs around the rate limiters? Interested
in how Cassandra could be used to serve/store data products re data mesh
and guardrails are super crucial re serving data to analytics users without
impacting operational performance. :)
On Fri, May 7, 2021 at 7:00 AM Jeff
I addition to Jeff's answer... Certificate hot reloading... For an
organization that uses annual certs :)
On Fri, May 7, 2021, 8:47 AM Durity, Sean R
wrote:
> There is not enough 4.0 chatter here. What feature or fix of the 4.0
> release is most important for your use case(s)/environment? What
My bad. It's V4, not v4. :)
Works fine with V4. Spews errors on V5.
-Joe
On 5/7/2021 12:16 PM, Joe Obernberger wrote:
So I'm confused.
I get this on startup from the client:
2021-05-07 15:27:48,119 WARNÂ
[com.dat.oss.dri.int.cor.poo.ChannelPool] (s1-admin-1)
So I'm confused.
I get this on startup from the client:
2021-05-07 15:27:48,119 WARNÂ [com.dat.oss.dri.int.cor.poo.ChannelPool]
(s1-admin-1) [s1|hercules/172.16.100.253:9042] Fatal error w
hile initializing pool, forcing the node down:
Those of y’all who have difficulty with Java 11, have you asked about it on the
mailing list or filed a Jira?
Dinesh
> On May 7, 2021, at 8:14 AM, Joe Obernberger
> wrote:
>
>
> I can retry Java 11.
>
> I am seeing this error a lot - still debugging, but I'll throw it out there -
> using
That's a driver error using protocol V5, which is the default from 4.0-rc1 but
only recently added to the drivers. Can you try specifying protocol V4 with all
the same parameters? Also, if it's at all possible (which it may not be, given
the divergence between driver versions 3 & 4), could you
I can retry Java 11.
I am seeing this error a lot - still debugging, but I'll throw it out
there - using 4.11.1 driver and a 4 node RC1 cluster. I'm seeing
warning in the cassandra logs about slow queries, but no errors. This
error is client side.
Caused by:
Cassandra 4.0 should work fine with java 11, including zgc (though zgc in
jdk11 isn't meant to be production ready).
The things I care most about:
- Much faster streaming, which you care about if you're not using
EBS/Disaggregated storage
- Virtual tables that make observability much more
;user@cassandra.apache.org"
Date: Friday, 7 May 2021 at 15:05
To: "user@cassandra.apache.org" , "Durity, Sean R"
Subject: Re: 4.0 best feature/fix?
Hi Sean - I'm using RC1 now in a research environment on bare metal. The
biggest drawback of Cassandra for me is that Cassandra has iss
Hi Sean - I'm using RC1 now in a research environment on bare metal.
The biggest drawback of Cassandra for me is that Cassandra has issues
working with modern large servers - a server with >32TBytes of SSD seems
to be a non-starter.
I tried running Cassandra with java 11, and that doesn't
12 matches
Mail list logo
