Closed SuhailRahman closed 3 years ago
@SuhailRahman you have some DNS or network policies issues as far as I can tell
...
Cannot get host id map: HTTP Request Failed: Post \"http://cassandra-wdc-1-dc1-rack1-0.cassandra-wdc-1:8778/jolokia/
....
lookup cassandra-wdc-1-dc1-rack2-0.cassandra-wdc-1 on 10.96.0.10:53: no such hostError while starting backup operation
The last log shows that it tried to do a backup but it failed to post the query to the backup sidecar
@cscetbon This works completely fine when both Cassandra clusters and the casskop operator are in same namespace.
@SuhailRahman yeah by default casskop watches its own namespace. You need to update WATCH_NAMESPACE
in order to get it to look at another namespace. https://github.com/Orange-OpenSource/casskop/blob/e3a6b29ff9223d99f0eb6d39cb5fc34ff96ed5b5/helm/cassandra-operator/templates/deployment.yaml#L52-L55
I have made those changes. Casskop is able to bring up pods in different namespace but there is a problem when backup operation is triggered.
What is the problem ? It should see the CassandraBackup and CassandraRestore objects and trigger operations.
Sorry for the late reply.
Here, I have the Cassandra cluster in namespace cassandra-ns
and the operator is present in cassandra-operator-ns
. http://cassandra-wdc-1-dc1-rack1-0.cassandra-wdc-1
is not reachable for some reason, I wanted to understand what is the significance of cassandra_seeds
, does it have any role with respect to backup operation, and is http://cassandra-wdc-1-dc1-rack1-0.cassandra-wdc-1
reachable to other namespaces.
@SuhailRahman seeds are not used specifically for a backup but only for new nodes to join an existing cluster. however nodes need to be reachable between namespaces otherwise it won't do anything. Do you have some network policies in place and you forgot to open the port used to connect to the backrest container ?
Closing the ticket until there is a way to reproduce the issue.
Type of question
About general context and help around casskop ?
Question
What did you do? I migrated the operator from namespace-scoped Operator to a cluster-scoped Operator. I deployed the casskop operator under the namespace
cassandra-operator-ns
and I deployed Cassandra Clusters under the namespacecassandra-ns
, as shown below.I created a backup operation for the Cassandra cluster deployed in
cassandra-ns
namespace.What did you expect to see? I was expecting to see the backup being initiated and backed up successfully.
What did you see instead? Under which circumstances? I was observing that backup was not getting initiated as the operator and Cassandra cluster are in different namespaces.
Logs of backrest Sidecar
Log of casskop operator