Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/hybrid/StorageGRID/Services/How_to_check_high_java_heap_usage_caused_by_merkle_tree_memory_leak_in_StorageGRID_11.4
      Applies to NetApp StorageGRID 11.4 Under certain circumstances, the version of Cassandra contained within the StorageGRID 11.4 codeline (DSE 5.1.14) can exhibit high java heap usage due to a merkle tr...Applies to NetApp StorageGRID 11.4 Under certain circumstances, the version of Cassandra contained within the StorageGRID 11.4 codeline (DSE 5.1.14) can exhibit high java heap usage due to a merkle tree memory leak caused by long-finished repairs. StorageGRID will report: High Java Heap alarms/alerts Cassandra repair errors in logs, example: [ERROR] org.apache.cassandra.repair.Validator:268 - Failed creating a merkle tree for [repair #e9a52ab0-9329-11eb-83c1-8bc0b64bffdd on storagegrid
    • https://kb.netapp.com/hybrid/StorageGRID/Maintenance/Upgrade_precheck_determines_additional_persistence_configuration_files
      Applies to StorageGRID Upgrades Issue When performing upgrade, precheck fails. "The following issues were identified by the Persistence list customizations precheck" "The list of persistence configura...Applies to StorageGRID Upgrades Issue When performing upgrade, precheck fails. "The following issues were identified by the Persistence list customizations precheck" "The list of persistence configuration files found on <node> did not match the expected list"
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/How_to_increase_StorageGRID_ILM_driven_erasure_coding_write_concurrency
      Applies to NetApp StorageGRID. StorageGRID software release 11.4 or newer. Description This procedure describes how to change the EC (Erasure Coding) Write Concurrency in StorageGRID. This may be need...Applies to NetApp StorageGRID. StorageGRID software release 11.4 or newer. Description This procedure describes how to change the EC (Erasure Coding) Write Concurrency in StorageGRID. This may be needed when EC writes are falling behind and cannot catch up with the ingest rate. That can result in ingested data to still be in Dual Commit weeks after ingesting.