Assuming the rebuild is happening on a node in another DC, then there
should not be an issue if you are using LOCAL_ONE. If the node is in the
local DC (i.e., same DC as the client), I am inclined to think repair would
be more appropriate than rebuild but I am not 100% certain.
On Mon, Aug 5,
No, not strictly sufficient - makes it much less likely though
A client may connect to another node and still send the request to that host if
the snitch picks it. You can make THAT less likely with some snitch trickery
(setting the badness for the rebuilding host) via jmx
> On Aug 5, 2019,
Hey guys,
Can you confirm that disabling the native transport (nodetool disablebinary) is
enough with Cassandra 3.11+ to avoid clients hitting inconsistent data on that
node when they use LOCAL_ONE consistency ? (Particularly when the node is
rebuilding …)
I'd like to avoid any fancy client
I think this might be because the timeout only applied to each request, and
the driver is paginating in the background. Each page is a new request.
On Mon, Aug 5, 2019, 12:08 AM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Mon, Aug 5, 2019 at 8:50 AM nokia ceph
> wrote:
>
>> Hi
DataStax has a very fast bulk load tool - dsebulk. Not sure if it is available
for open source or not. In my experience so far, I am very impressed with it.
Sean Durity – Staff Systems Engineer, Cassandra
-Original Message-
From: p...@xvalheru.org
Sent: Saturday, August 3, 2019 6:06
Hi all,
We’ve been running a production grade cluster with 21 nodes for the past few
weeks. We use the COPY TO method to export our data.
The thing we are seeing, is that this gives an inconsistent amount of records.
On day 1 we get 1.1mil records and the next 900k. On day 3 we see 1mil and
On Mon, Aug 5, 2019 at 8:50 AM nokia ceph wrote:
> Hi Community,
>
> I am using Cassanadra 3.0.13 . 5 node cluster simple topology. Following
> are the timeout parameters in yaml file:
>
> # grep timeout /etc/cassandra/conf/cassandra.yaml
> cas_contention_timeout_in_ms: 1000
>
Hi Community,
I am using Cassanadra 3.0.13 . 5 node cluster simple topology. Following
are the timeout parameters in yaml file:
# grep timeout /etc/cassandra/conf/cassandra.yaml
cas_contention_timeout_in_ms: 1000
counter_write_request_timeout_in_ms: 5000
cross_node_timeout: false