The error message indicates source side stream session failed. if
source side load is heavy, consider reduce some, like stop repair, etc. If
every trying failed at same file, may check that file too. Hope it helps.
On Wed, Oct 6, 2021 at 11:20 PM MyWorld wrote:
> Hi Jim,
> It's 600 Megabits
The "workaround" (it's a proper fix) is to upgrade the libgnutls30 package.
On 07/10/2021 15:24, rhys.campb...@swisscom.com wrote:
Thanks for that.
This command is actually spat out by the apt_key ansible module….
but I'm sure there's a way around it.
Cheers,
R
*From:*Bowen Song
*Sent:*
Thanks for that.
This command is actually spat out by the apt_key ansible module….
but I'm sure there's a way around it.
Cheers,
R
From: Bowen Song
Sent: 07 October 2021 14:05
To: user@cassandra.apache.org
Subject: Re: Problem with www.apache.org/dist/cassandra/KEYS?
Well...
$ wget -qO - ht
There was a problem with keys reported yesterday on ASF Slack that Brandon
Williams (driftx) fixed early in my morning (I'm based in Australia).
Perhaps try again. For reference, the Slack conversation is available here
-- https://the-asf.slack.com/archives/CJZLTM05A/p1633538881180500. Cheers!
>
Well...
$ wget -qO - https://www.apache.org/dist/cassandra/KEYS | wc -c
0
The first part of the command is clearly not working. Removing the "-q",
and "wget" shows the error message:
$ wget -O - https://www.apache.org/dist/cassandra/KEYS
--2021-10-07 12:03:34-- https://www.apache.
Hi it's my point as we have only one way to insert data it seems be cool
to set it by code to allow change it by configuration if need.
I use another way to clean my cluster : I down a node, delete bad
sstables manually, up & repair the node. And apply it node by node.
Now the nodes don't con
