Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • StorageGRID Erasure coding rebalance procedure is progressing too slow
      https://kb.netapp.com/hybrid/StorageGRID/Performance/StorageGRID_Erasure_coding_rebalance_procedure_is_progressing_too_slow
      Applies to StorageGRID 11.5 Erasure Coding (EC) Issue Poor performance during EC rebalance procedure.
    • Poor client performance but ONTAP latency is good - Resolution Guide
      https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Poor_client_performance_but_ONTAP_latency_is_good_-_Resolution_Guide
      KB article provides steps to investigate network latency when High-end user latency reported from Internal monitoring software, Low throughput/Poor Performance reported by end users and Data ONTAP and...KB article provides steps to investigate network latency when High-end user latency reported from Internal monitoring software, Low throughput/Poor Performance reported by end users and Data ONTAP and NetApp monitoring tools show low latency.
    • Slow performance on cifs flexgroup volume
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Slow_performance_on_cifs_flexgroup_volume
      Applies to ONTAP 9 FlexGroup Issue Slow performance on CIFS FlexGroup volume
    • StorageGRID appliance performance degradation following E-Series upgrade to 11.70.1GA
      https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/StorageGRID_appliance_performance_degradation_following_E-Series_upgrade_to_11.70.1GA
      StorageGRID appliances that match above criteria may experience significant performance degradation after upgrade to 11.70.1GA. Storage node appliance unplanned reboot highlighted by node down related...StorageGRID appliances that match above criteria may experience significant performance degradation after upgrade to 11.70.1GA. Storage node appliance unplanned reboot highlighted by node down related alerts "Unable to communicate with node". The storage node base OS syslog indicates the node was rebooted by the slow I/O monitoring script as a recovery mechanism: