You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Dinesh Chitlangia (Jira)" <ji...@apache.org> on 2021/02/14 04:50:00 UTC
[jira] [Resolved] (HDDS-4798) Unexpected update of container's
bcsID in BlockManagerImpl
[ https://issues.apache.org/jira/browse/HDDS-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Chitlangia resolved HDDS-4798.
-------------------------------------
Fix Version/s: 1.2.0
Resolution: Fixed
> Unexpected update of container's bcsID in BlockManagerImpl
> ----------------------------------------------------------
>
> Key: HDDS-4798
> URL: https://issues.apache.org/jira/browse/HDDS-4798
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Janus Chow
> Assignee: Janus Chow
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> In BlockManagerImpl.putBlock, there is a special case that BlockData's BlockCommitSequenceId could be 0. The reason should be as the comment:
> {code:java}
> // default blockCommitSequenceId for any block is 0. It the putBlock
> // request is not coming via Ratis(for test scenarios), it will be 0.
> // In such cases, we should overwrite the block as well
> {code}
> But after the Block with bcsId as 0 is updated, the container's bcsId will also be updated to 0. If there is no such special case, the container's bscId should always increase, but with this case, the container's bcsId could decrease to 0.
> This ticket is to add a check before updating the container's bcsId.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org