[ https://issues.apache.org/jira/browse/HDDS-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanisha Koneru resolved HDDS-2980. ---------------------------------- Resolution: Fixed > Delete replayed entry from OpenKeyTable during commit > ----------------------------------------------------- > > Key: HDDS-2980 > URL: https://issues.apache.org/jira/browse/HDDS-2980 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: HA, Ozone Manager > Reporter: Hanisha Koneru > Assignee: Hanisha Koneru > Priority: Blocker > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > During KeyCreate (and S3InitiateMultipartUpload), we do not check the > OpenKeyTable if the key already exists. If it does exist and the transaction > is replayed, we just override the key in OpenKeyTable. This is done to avoid > extra DB reads. > During KeyCommit (or S3MultipartUploadCommit), if the key was already > committed, then we do not replay the transaction. This would result in the > OpenKeyTable entry to remain in the DB till it is garbage collected. > To avoid storing stale entries in OpenKeyTable, during commit replays, we > should check the openKeyTable and delete the entry if it exists. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org