Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Delete File Communication uses the general communication pattern with an IdentifyPillarsForDelete and a Delete Primitive. May also include a confirmation, finalisation and Undelete part. To be analysed.

Delete from Bit Repository

Delete File communication starts as the general communication pattern

  • Client sends IdentifyPillarsForDeleteFileRequest message with data ID, and all pillars in SLA reply with IdentifyPillarsForDeleteFileReply messages
  • Client sends DeleteFileRequest messages with data ID to all identified pillars and all pillars in reply with DeleteFileReply messages

It is not currently decided whether data will now be deleted on the specified pillar or on the repository and DeleteFileComplete messages sent, or do we want a two-phase commit where the data is now in an 'under deletion state' and the client must send a delete confirmation before the pillars finalise the deletion.

See also Undelete under Delete Design Discussions

Delete Copy from Pillar

Delete File communication in connection with integrity corrective action does not follow the pattern, as the pillar on which we want to delete a copy has already been identified. The communication then starts with the DeleteFileRequest message.

  • No labels