> so can cause repairs to deadlock forever
Small correction, I finished fixing the tests in CASSANDRA-19042 and we don’t
deadlock, we timeout and fail repair if any of those messages are dropped.
> On Feb 13, 2024, at 11:04 AM, David Capwell wrote:
>
>> and to point potential users that are
> and to point potential users that are evaluating the technology to an
> optimized set of defaults
Left this comment in the GH… is there a reason all guardrails and reliability
(aka repair retries) configs are off by default? They are off by default in
the normal config for backwards compatib
+1 to deprecating dual ports and removing in 5.0
On Tue, Feb 13, 2024 at 4:29 AM Štefan Miklošovič <
stefan.mikloso...@gmail.com> wrote:
> Alright ... so how I am interpreting this, even more so after Sam's and
> Brandon's mail, is that we should just get rid of that completely in trunk
> and de
Hi All,
CASSANDRA-18753 introduces a second set of defaults (in a separate
"cassandra_latest.yaml") that enable new features of Cassandra. The
objective is two-fold: to be able to test the database in this
configuration, and to point potential users that are evaluating the
technology to an optimiz
I am kindly pinging people that we still have some work to do here.
Currently, we are missing at least one more binding +1.
Regards
On Fri, Feb 9, 2024 at 5:08 AM Paulo Motta wrote:
> +1
>
> Reviewed changelog + tested docker image build (verify binary
> gpg+sha512sum) + jre11 startup.
>
> On T
Alright ... so how I am interpreting this, even more so after Sam's and
Brandon's mail, is that we should just get rid of that completely in trunk
and deprecate in 5.0.
There are already patches for 3.x and 4.x branches of the driver so the way
I was looking at that was that we might resurrect th
On Tue, Feb 13, 2024 at 6:17 AM Sam Tunnicliffe wrote:
> Also, if CASSANDRA-16999 is only going to trunk, why can't we just deprecate
> dual ports in 5.0 (as it isn't at -rc stage yet) and remove it from trunk?
> That seems preferable to shoehorning something into the new
> system_views.peers t
Late to the party I'm afraid, but I'd agree with Abe's proposal to deprecate
the dual port approach given that CASSANDRA-10559 makes it pretty much
redundant. Adding further yaml options like "default ssl/no ssl" feels like
another nasty band-aid that we'll have to live with for the foreseeable
