CQL Copy command will not work in case if you are trying to copy from all
NODES because COPY command will check all N nodes UP and RUNNING Status.
If you want to complete then you have 2 options:-
1) Remove DOWN NODE from COPY command
2) Make it UP and NORMAL status.
On Mon, Jul 2, 2018 at 9:15
Hi,
The error shows that, the cqlsh connection with down node is failed.
So, you should debug why it happened.
Although, you have mentioned other node in cqlsh command '10.0.0.154'
my guess is, the down node was present in connection pool, hence it was
attempted for connection.
Ideally the avail
nodetool repair -pr on every node --- covered all ranges of data.
On Sun, Jul 1, 2018 at 7:03 AM, Riccardo Ferrari wrote:
> Hi list,
>
> After long time of operation we come to the need of growing our cluster.
> This cluster was born on 2.X and almos 2 years ago migrated to 3.0.6 ( I
> kno
Hi list,
After long time of operation we come to the need of growing our cluster.
This cluster was born on 2.X and almos 2 years ago migrated to 3.0.6 ( I
know we are bit prudent )
The cluster was a 3 m1.xlarge (we are on AWS) and table RF was 3
Thanks to your valuable hints we added a new node
Hi,
Thank you so much for answer.
Please, is it possible to use this command ?
nodetool status mykeyspace
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad Tokens OwnsHost ID
Rack
UN 127.0.0.1 47.66 KB
Thanks for the recommendation Jeff, I'll try to get a heap dump next time
this happens and try the other changes in the mean time.
Also not sure but this CASSANDRA-13900 looked it might be related.
On Sat, Jun 30, 2018 at 9:51 PM, Jeff Jirsa wrote:
> The young gcs loom suspicious
>
> Without se
