Skip to main content
Hitachi Vantara Knowledge

Considerations for deleting an erasure coding topology

These considerations apply to deleting an erasure coding topology:

  • You can delete an erasure coding topology only while either of these is true:
    • At least one system in the topology is available, the total number of erasure-coded objects and erasure-coded parts of multipart objects on each available system is zero, and the state of the topology is retired. These are the normal conditions for deleting a topology.
    • No more than one system in the topology is unavailable, the total number of erasure-coded objects and erasure-coded parts of multipart objects on each available system is zero, and the state of the topology is retiring. In this case, you are prompted to confirm the delete request.
      ImportantDeleting an erasure coding topology under these conditions may result in inaccessible data in namespaces on the unavailable system, even if those namespaces are configured to be compliant. You should delete the topology only if that system is no longer needed. If the system is still needed, wait to delete the topology until the topology has finished retiring on all systems.
  • You cannot delete an erasure coding topology while either of these is true:
    • The total number of erasure-coded objects and erasure-coded parts of multipart objects on any available system in the topology is greater than zero.

      The Management panel on the EC Topologies page for a retiring or retired topology shows the number of erasure-coded objects and erasure-coded parts of multipart objects on the available systems.

    • More than one system in the topology is unavailable, and the state of the topology is retiring.

 

  • Was this article helpful?