[HDDS-4352] Container info is not correct when there is QUASI_CLOSED replica

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Done
• Assignee: Ashish Kumar
• Reporter: Sammi Chen
• Created: 15/Oct/20 07:24
• Updated: 21/Jan/24 15:45
• Resolved: 07/Aug/23 07:53

Description

When all the blocks are deleted in the container, "usedBytes" and "numberOfKeys" are expected to be "0". But there are following containers found. All of them are previsouly on QUASI_CLOSED state.

{
  "state" : "CLOSED",
  "replicationFactor" : "THREE",
  "replicationType" : "RATIS",
  "usedBytes" : 0,
  "numberOfKeys" : -1,
  "lastUsed" : "2020-10-13T06:35:24.678Z",
  "stateEnterTime" : "2020-10-10T12:06:35.445Z",
  "owner" : "0097000b-519c-4e11-b20c-a6e657a4b7c9",
  "containerID" : 11,
  "deleteTransactionId" : 1555,
  "sequenceId" : 0,
  "open" : false
}

{
  "state" : "CLOSED",
  "replicationFactor" : "THREE",
  "replicationType" : "RATIS",
  "usedBytes" : 33554432,
  "numberOfKeys" : 0,
  "lastUsed" : "2020-10-13T06:35:24.678Z",
  "stateEnterTime" : "2020-10-10T12:06:35.663Z",
  "owner" : "0097000b-519c-4e11-b20c-a6e657a4b7c9",
  "containerID" : 16,
  "deleteTransactionId" : 1532,
  "sequenceId" : 0,
  "open" : false
}

Issue Links

• relates to: HDDS-8129 ContainerStateMachine allows two different tasks with the same container id running in parallel