[
https://issues.apache.org/jira/browse/HDDS-10736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842173#comment-17842173
]
Wei-Chiu Chuang commented on HDDS-10736:
----------------------------------------
Yes inconsistency is possible.
Another scenario is when there are two clients
client 1 opens "file1" writes some data and then the client sleep for some time
while
client 2 opens "file1" writes some data, do hsync.
At this point, if client 1 comes back and hsync, it could potentially overwrite
client 2's data.
It doesn't look like we prevent this scenario in the code.
> [hsync] OMKeyCommitRequest should reject if client id doesn't match
> -------------------------------------------------------------------
>
> Key: HDDS-10736
> URL: https://issues.apache.org/jira/browse/HDDS-10736
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Wei-Chiu Chuang
> Assignee: Chung En Lee
> Priority: Major
>
> https://github.com/apache/ozone/blame/f4d771647e7aac2a9095da6f96413fc4a96df838/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/OMKeyCommitRequest.java#L240
> There appears to be a pontential bug in OMKeyCommitRequest/
> OMKeyCommitRequestWithFSO, where
> it doesn't verify the client id attached in the CommitRequest is the same as
> the client id in the OMKeyInfo in the key table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
