t some sort of write-only is appropriate.
Thanks,
Thomas
From: Nicolas Guyomar [mailto:nicolas.guyo...@gmail.com]
Sent: Mittwoch, 18. Oktober 2017 09:58
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Not serving read requests while running nodetool repair
Hi Th
propriate.
>
> Thanks,
> Thomas
>
> From: Nicolas Guyomar [mailto:nicolas.guyo...@gmail.com]
> Sent: Mittwoch, 18. Oktober 2017 09:58
> To: user@cassandra.apache.org
> Subject: Re: Not serving read requests while running nodetool repair
>
> Hi Thomas,
>
> AF
thinks
that some sort of write-only is appropriate.
Thanks,
Thomas
From: Nicolas Guyomar [mailto:nicolas.guyo...@gmail.com]
Sent: Mittwoch, 18. Oktober 2017 09:58
To: user@cassandra.apache.org
Subject: Re: Not serving read requests while running nodetool repair
Hi Thomas,
AFAIK temporarily reading
Hi Thomas,
AFAIK temporarily reading at LOCAL_QUORUM/QUORUM until nodetool repair is
finished is the way to go. You can still disable binary/thrift on the node
to "protect" it from acting as a coordinator, and complete its repair
quietly, but I'm not sure that would make such a huge difference in
Hello,
due to performance/latency reasons, we are currently reading and writing time
series data at consistency level ONE/ANY.
In case of a node being down and recovering after the default hinted handoff
window of 3 hrs, we may potentially read stale data from the recovering node.
Of course,
