Janus Chow created HDDS-4798:
--------------------------------
Summary: 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
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: [email protected]
For additional commands, e-mail: [email protected]
