Dataminer upgrade error – ‘Cassandra.Cluster’ threw an exception

Solved757 viewsCouldn't remove Cassandra table DataMiner V10.2.7.0-11922 initializer for 'Cassandra.Cluster' threw an exception
1
0 Comments

Hello, after a recent upgrade at DAZN we received the following exception error

|error|Couldn't remove Cassandra table. Cause: The type initializer for 'Cassandra.Cluster' threw an exception..

This was reported after upgrading to DataMiner V10.2.7.0-11922 (from V10.2CU2-1164). This same error has been generated across two independent system upgrades (both systems comprising a single pair of DMAs with Cassandra databases that reside on the DMA servers). On both occasions after the upgrade, Dataminer runs and appears to function as expected.

Are there any thoughts as to the cause of the error please?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 12th July 2023

1 Answer

3
12.26K 1 Comment

Hi Paul,

You can find some more information on this through the following topic:

Upgrade to 10.2.7 feature release shows an error in the log - DataMiner Dojo

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 12th July 2023
Srikanth Mandava [SLC] [DevOps Advocate] commented

I have posted the question based on the issue reported from DAZN. Paul, it’s the same question and context. Thanks.
You are viewing 1 out of 1 answers, click here to view all answers.