StorageGRID Cassandra service not starting after storage node crash/reboot e this error and continue starting the node ignoring commit log replay problems, specify -Dcassandra.commitlog.ignorereplayer...StorageGRID Cassandra service not starting after storage node crash/reboot e this error and continue starting the node ignoring commit log replay problems, specify -Dcassandra.commitlog.ignorereplayerrors=true on the command line If you wish to override this error and continue starting the node ignoring commit log replay problems, specify -Dcassandra.commitlog.ignorereplayerrors=true on the command line 2022-08-23 14:55:29 +0000 | ade-exporter | waiting for dds, waiting 30s to try again
Applies to NetApp StorageGRID Issue S3 clients might be not able to access data within buckets and receive error: ServiceUnavailable: Please reduce your request rate
Applies to NetApp StorageGRID 11.3 Issue Cassandra QueryException error seen in the system logs: ERROR 0242 SCAN: Cassandra QueryException (Failed to execute cql: SELECT event_time, event, last_access...Applies to NetApp StorageGRID 11.3 Issue Cassandra QueryException error seen in the system logs: ERROR 0242 SCAN: Cassandra QueryException (Failed to execute cql: SELECT event_time, event, last_access_time, user_metadata, writetime(user_metadata), content_type, writetime(content_type) FROM storagegrid.object_by_uuid WHERE uuid =xxxxx-xxxxxxx-xxxxxxxx-xxxxxxx- Cassandra Driver Error(Read failure):'Operation failed - received 1 responses and 2 failures')
Applies to StorageGRID 11.2 and above Issue Cassandra service is in error state Storage Node is showing Blue in GRID GUI In Cassandra system.log you see the following message: Mutation checksum failur...Applies to StorageGRID 11.2 and above Issue Cassandra service is in error state Storage Node is showing Blue in GRID GUI In Cassandra system.log you see the following message: Mutation checksum failure at 11504079 in Next section at 11504079 in CommitLog-x-xxxxxxxxxxxxx.log
Applies to NetApp StorageGRID 11.x Issue Alarms page is reporting SMTT (Total Events) with description "At least 10". One or more storage nodes are reporting "Cassandra unhandled exceptions" from the ...Applies to NetApp StorageGRID 11.x Issue Alarms page is reporting SMTT (Total Events) with description "At least 10". One or more storage nodes are reporting "Cassandra unhandled exceptions" from the Nodes page.
Applies to NetApp StorageGRID 11.x Issue Listing all objects from a bucket takes a long time after deleting a large amount of objects from the bucket even if there is only a small amount of objects le...Applies to NetApp StorageGRID 11.x Issue Listing all objects from a bucket takes a long time after deleting a large amount of objects from the bucket even if there is only a small amount of objects left
Cassandra reaper repair list from reaper_commands.txt in lumberjack collection of storage node(s) or by running this command spreaper --reaper-host=localhost --reaper-port=9403 status-cluster storageg...Cassandra reaper repair list from reaper_commands.txt in lumberjack collection of storage node(s) or by running this command spreaper --reaper-host=localhost --reaper-port=9403 status-cluster storagegrid in SSH session to a storage node, indicates that some or all keyspaces' repairs contain the following message for the last event:
Metadata-only storage node CPU and memory configuration should match the nodes in the StorageGRID site they are being added to or better. When deploying a metadata-only storage node virtual machine (V...Metadata-only storage node CPU and memory configuration should match the nodes in the StorageGRID site they are being added to or better. When deploying a metadata-only storage node virtual machine (VM), modify the VM settings to include a minimum of 64GB of memory. To maximize metadata capacity and provide optimal performance, the VM should include at least 128GB of RAM and 40 vCPU.
A non-clean reboot or shutdown of a Storage Node due to power failure, hardware fault, Linux kernel panic, or other such events can lead to Cassandra failing to start. ERROR [main] 2019-09-26 23:29:20...A non-clean reboot or shutdown of a Storage Node due to power failure, hardware fault, Linux kernel panic, or other such events can lead to Cassandra failing to start. ERROR [main] 2019-09-26 23:29:20,818 CassandraDaemon.java (line 725) Cannot remove temporary or obsoleted files for storagegrid.s3_usage_delta due to a problem with transaction log files.
Applies to StorageGRID 11.4.0.x and later Issue Cassandra Reclaimable Space diagnostic alerts reported for storagegrid_auto_compactor_effective_shadow_percentage
