[HDDS-4037] Incorrect container numberOfKeys and usedBytes in SCM after key deletetion

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Labels: pull-request-available
• Target Version/s: 1.1.0
• Assignee: Sammi Chen
• Reporter: Sammi Chen
• Created: 27/Jul/20 13:38
• Updated: 27/Jan/22 22:21
• Resolved: 13/Aug/20 06:21

Description

bin/ozone admin container list -s=3 -c=1

{ "state" : "CLOSED", "replicationFactor" : "THREE", "replicationType" : "RATIS", "usedBytes" : 2153526137, "numberOfKeys" : 57, "lastUsed" : "2020-07-27T13:37:16.305Z", "stateEnterTime" : "1970-01-10T08:12:26.645Z", "owner" : "a46123a8-be63-4736-9478-ce4d8ac845cc", "containerID" : 4, "deleteTransactionId" : 799549, "sequenceId" : 0, "open" : false }

`-- 4

	– chunks
`-- metadata
	– 4-dn-container.db
		– 000052.sst
		– 000121.log
		– CURRENT
		– IDENTITY
		– LOCK
		– LOG
		– LOG.old.1574862506326174
		– LOG.old.1575885724469410
		– LOG.old.1579433296221409
		– LOG.old.1583661885934875
		– LOG.old.1583669077602829

Issue Links

• Dependent: HDDS-4023 Delete closed container after all blocks have been deleted
• fixes: HDDS-3432 Enable TestBlockDeletion test cases
• relates to: HDDS-5359 Incorrect BLOCKCOUNT and BYTESUSED in container DB
• links to: GitHub Pull Request #1295