Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/What_is_the_difference_between_Consistency_level_Read_after_new_write_and_Available
      Available (eventual consistency for HEAD operations) Behaves the same as the Read-after-new-write consistency level, but only provides eventual consistency for HEAD operations. Note: From 11.5.0.3, no...Available (eventual consistency for HEAD operations) Behaves the same as the Read-after-new-write consistency level, but only provides eventual consistency for HEAD operations. Note: From 11.5.0.3, non-existent GET matches to HEAD to return 404 when bucket consistency is set to Available Behaves the same as the Read-after-new-write consistency level, but provides eventual consistency for HEAD and GET operations.
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_long_should_slice_and_block_drives_remain_logically_out_of_an_Element_OS_cluster
      If only a single slice drive remains in Available status for a period of time, this causes an extra amount of workload on the cluster as all of the primary iSCSI sessions for the data on the node are ...If only a single slice drive remains in Available status for a period of time, this causes an extra amount of workload on the cluster as all of the primary iSCSI sessions for the data on the node are being redirected to a different node in the cluster. If the node only has this fault condition, we strongly encourage our customers to from the cluster UI, proceed to add the drives back to the cluster to bring the node back to a Healthy status.