Thanks Guys!
Sorry for the late reply.
I'm interested in TWCS where I understand is more stable in 3.11.1 than in
3.0.15, tombstone compaction and slow logs.
I don't plan to use MVs and SASI in the near future, as I understand are
not Production ready.
Is it okay to use the above features?
Hi guys,
Could anyone please help on this simple question?
How to check C* partition size and related information.
looks nodetool ring only shows the token distribution.
Thanks
nodetool cfstats
nodetool cfhistograms
--
Jeff Jirsa
> On Jan 7, 2018, at 7:26 AM, Peng Xiao <2535...@qq.com> wrote:
>
> Hi guys,
>
> Could anyone please help on this simple question?
> How to check C* partition size and related information.
> looks nodetool ring only shows the token distrib
There’s a tweak to TWCS in 3.11.1 that lets data expire faster, but I wouldn’t
call it unstable in any version I’ve ever used it with. I’ve deployed it on
2.0, 2.1, 2.2 [1], and used it in every version of C* that we’ve shipped it,
and have never had an issue.
I would put 3.11.1 in prod over
If you're on 3.9 it's likely unrelated as streaming_socket_timeout_in_ms is
48 hours. Appears rebuild is trying to stream the same file twice. Are
there other exceptions in the logs related to the file, or can you find out
if it's previously been sent by the same session? Search the logs for the
fi
Hi,
Can you please provide dome JIRAs for superior fixes and performance
improvements which are present in 3.11.1 but are missing in 3.0.15.
In addition,could you also provide the probable implications of the open
memory leak issue in Cassandra 3.11.
CASSANDRA-13929: BTree$Builder / io.netty.util
None are essential. Cassandra will gracefully shutdown in any scenario as
long as it's not killed with a SIGKILL. However, drain does have a few
benefits over just a normal shutdown. It will stop a few extra services
(batchlog, compactions) and importantly it will also force recycling of
dirty comm
The sequence does have some objective benefits - especially stopping transports
and then gossip, it tells everything you’re going offline before you do, so
requests won’t get dropped or have to speculate to other replicas.
--
Jeff Jirsa
> On Jan 7, 2018, at 7:22 PM, kurt greaves wrote:
>