Skip to main content
NetApp Knowledge Base

StorageGRID EC rebalance-data fails with Could not connect to Cassandra cluster

Views:
202
Visibility:
Public
Votes:
0
Category:
storagegrid-webscale
Specialty:
sgrid
Last Updated:

Applies to

NetApp StorageGRID 11.5

Issue

The StorageGRID rebalance-data script fails with a “Could not connect to Cassandra cluster” error. For example:

# rebalance-data start --site site1
Request to rebalance 12612345:10.xx.xx.xx, 12712345:xx.xx.xx, 12512345:xx.xx.xx, 12812345:xx.xx.xx, 12912345:xx.xx.xx
Unable to connect to Cassandra cluster via sg-a: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-b: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-c: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-d: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-1: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-2: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-3: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-4: execution expired. Trying next node...
Unable to connect to Cassandra cluster via sg-5: execution expired. Trying next node...
/usr/local/sbin/ec-rebalance.rb:715:in `block in <main>': Could not connect to Cassandra cluster. (RuntimeError)
from /usr/lib/ruby/2.5.0/tmpdir.rb:93:in `mktmpdir'
from /usr/local/sbin/ec-rebalance.rb:692:in `<main>'
Requested rebalance operation failed.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.