Spotted this kind of error in a local cassandra deployment (no cassandra cluster, DB on the DMA):
what's the impact on the DMA when one or more "storages" go to offload mode?
Is it correct to configure this as a critical alarm? Or should it be some lower severity?
Any steer will be helpful - thanks
Hi Alberto,
These kind of alarms get generated when the DataMiner system loses contact with the database. To prevent data loss we then go into a failsafe mode where data is stored on disk (C:\Skyline DataMiner\Offload\OfflaodedData.sqlite3). Once the conenction is restored the data in these files will be moved to the Database.
As long as these alarms are active it means that the system is either unable to connect to the database or in the process of moving the data to the DataBase.
Since this can impact the speed of the system and cause certain actions to fail, it seem sensible to have these marked as critical. Further investigation will need to be done to figure out why the system went into this failsafe mode. Things to check here are.
Is the cassandra service up, running and reachable
What errors does SLDBConnection.txt show
What errors does SLCassandraHealth.txt show
Thanks for the prompt feedback, Brent – much appreciated
Will follow up with the assigned squad.
It was an odd one as the DB is local, but could see that little by little many storages were impacted – please, is there any section where I can check how many storages are defined for my Cassandra instance?
Is 22 the maximum or would there be more that in this case were not failing?