When we are starting the node, it is starting bootstrap automatically and
restreaming the whole data again. It is not resuming .
On Thu, May 7, 2020 at 4:47 PM Adam Scott wrote:
> I think you want to run `nodetool bootstrap resume` (
> https://cassandra.apache.org/doc/latest/tools/nodetool/boot
I think you want to run `nodetool bootstrap resume` (
https://cassandra.apache.org/doc/latest/tools/nodetool/bootstrap.html) to
pick up where it last left off. Sorry for the late reply.
On Thu, May 7, 2020 at 2:22 PM Surbhi Gupta
wrote:
> So after failed bootstrapped , if we start cassandra ag
So after failed bootstrapped , if we start cassandra again on the new node
, will it resume bootstrap or will it start over?
On Thu, 7 May 2020 at 13:32, Adam Scott wrote:
> I recommend it on all nodes. This will eliminate that as a source of
> trouble further on down the road.
>
>
> On Thu, Ma
I recommend it on all nodes. This will eliminate that as a source of
trouble further on down the road.
On Thu, May 7, 2020 at 1:30 PM Surbhi Gupta
wrote:
> streaming_socket_timeout_in_ms is 24 hour.
> So tcp settings should be changed on the new bootstrap node or on all
> nodes ?
>
>
> On Th
streaming_socket_timeout_in_ms is 24 hour.
So tcp settings should be changed on the new bootstrap node or on all
nodes ?
On Thu, 7 May 2020 at 13:23, Adam Scott wrote:
>
> *edit
> /etc/sysctl.confnet.ipv4.tcp_keepalive_time=60
> net.ipv4.tcp_keepalive_probes=3net.ipv4.tcp_keepalive_intvl=10*
*edit
/etc/sysctl.confnet.ipv4.tcp_keepalive_time=60
net.ipv4.tcp_keepalive_probes=3net.ipv4.tcp_keepalive_intvl=10*
then run sysctl -p to cause the kernel to reload the settings
5 minutes (300) seconds is probably too long.
On Thu, May 7, 2020 at 1:09 PM Surbhi Gupta
wrote:
> [root@abc cassand
heck if [streaming_socket_timeout_in_ms ] setting in Cassandra.yaml file if
that sufficient enough before streaming is interrupted ?
~Asad
From: Surbhi Gupta [mailto:surbhi.gupt...@gmail.com]
Sent: Thursday, May 7, 2020 3:09 PM
To: user@cassandra.apache.org
Subject: Re: Bootstraping is failin
[root@abc cassandra]# cat /proc/sys/net/ipv4/tcp_keepalive_time
300
[root@abc cassandra]# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
30
[root@abc cassandra]# cat /proc/sys/net/ipv4/tcp_keepalive_probes
9
On Thu, 7 May 2020 at 12:32, Adam Scott wrote:
> Maybe a firewall killing a connection?
Maybe a firewall killing a connection?
What does the following show?
cat /proc/sys/net/ipv4/tcp_keepalive_time
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
cat /proc/sys/net/ipv4/tcp_keepalive_probes
On Thu, May 7, 2020 at 10:31 AM Surbhi Gupta
wrote:
> Hi,
>
> We are trying to expand a datacente
Thank you all,
I assume, my new node is used as coordinator, since all other nodes
are under heavy write load.
I need to spare some space for hints folder.
Regards,
Osman
On Thu, 7 May 2020 at 08:29, Jeff Jirsa wrote:
>
> Incremental bootstrap patch changed the logic here. A node can act as a
>
Hi,
We are trying to expand a datacenter and trying to add nodes but when node
is bootstrapping , it goes half way through and then fail with below error,
We have increased stremthroughput from 200 to 400 when we were trying for
the 2nd time but still it failed. We are on 3.11.0 , using G1GC with
Hi,
I don't believe that the peers entry is responsible for that exception.
Looking at the driver code, I can't even think of a scenario where that
exception would be thrown... I will run some tests in the next couple of
days to try and figure something out.
One thing that is certain from those l
Perfect, thanks for looking into this!
Best,
Matthias
5. Mai 2020, 20:01 von erik.mer...@datastax.com:
> Matthias,
>
> Thanks for sharing your findings and test code. We were able to track this to
> a regression in the underlying Netty library and already have a similar issue
> reported here:
I am having trouble with getting a list including maps with |Cassandra
Java Driver|.
For below version:
|List>myList
=state.getList(5,TypeTokens.mapOf(Integer.class,Integer.class));|
The error is like:
|InvalidRequest:Errorfrom server:code=2200[Invalidquery]message="Java
source compilation
Hi Chuck,
On Thu, May 7, 2020 at 10:14 AM Check Peck wrote:
> I have a scylla table as shown below:
>
(Please note that this is the Apache Cassandra users mailing list. Of
course, the feature is the same, so let me answer it here.)
>
> cqlsh:sampleks> describe table test;
>
>
> CREATE
In your schema case, for each client_id you will get a single 'when'
row. Just one. Even when there are multiple rows (clustering keys)
On Thu, May 7, 2020 at 12:14 AM Check Peck wrote:
>
> I have a scylla table as shown below:
>
>
> cqlsh:sampleks> describe table test;
>
>
> CREATE TABLE
I have a scylla table as shown below:
cqlsh:sampleks> describe table test;
CREATE TABLE test (
client_id int,
when timestamp,
process_ids list,
md text,
PRIMARY KEY (client_id, when) ) WITH CLUSTERING ORDER BY (when DESC)
AND bloom_f
17 matches
Mail list logo
