High latency at table level could be a result of no of factors.
High tombstones
GC
Bloom filter fp
I/O bottleneck
Insufficient cache or threads
Since your partion size is not a problem here, try running major
compaction on this table.
Also you can turn on caching for this table.
As mentioned abov
Whoops - had it in the wrong datacenter. Same issue - new node is
stuck in UJ, but I can start/stop OK with systemctl.
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address                   Load      Â
To
When I try to halt the joining node with systemctl stop cassandra, it
hangs. I don't see it doing any network, disk, or CPU activity using
tools like iotop, atop, and top.
I ended up kill -9'ing the process. I tried the same join on a
different machine, and the same issue occurs. It hangs i
Have an existing 5 node RC1 cluster and trying to join two more nodes to it.
The new node is stuck in the UJ status:
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address        Load       Tokens Owns
(effective)Â H
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)
[s1|hercules/172.16.100.2
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:
com.datastax.oss.driver.api.core.UnsupportedProtocolVersion
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 t
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: com.datastax.oss.driver.api.c
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 consiste
I have not tried to run 4.0 with Java 11, but according to the Docker image it
is running with Java 11, see here for reference
https://github.com/docker-library/cassandra/blob/f00a725cc0189ef166ac1d893227651bd81a6996/4.0/Dockerfile
-Tobias
From: Joe Obernberger
Reply to: "user@cassandra.apache
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 app
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 is working well so far?
What needs more work? Is there anything that needs more explanation?
[cid:image001.png@01D7431D.8C1332E0]
Sean Durity
Staff Systems Engine
Hi Sean,
thanks for the quick answer. I have applied your suggestion and tested on
several environments, everything is working fine.
Other communication protected by SSL such as server-to-server and
client-to-server is working without problems as well.
Regards,
Maxim.
On Fri, Apr 30, 2021 at 3:1
14 matches
Mail list logo
