You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2023/09/28 20:48:00 UTC
[jira] [Commented] (HDDS-9366) Only the Ratis leader DataNode should verify ACL and block token
[ https://issues.apache.org/jira/browse/HDDS-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770217#comment-17770217 ]
Wei-Chiu Chuang commented on HDDS-9366:
---------------------------------------
The pink area is ContainerCommandRequestProto.parseFrom(). 47% of overall overhead is in it.
!Screen Shot 2023-09-28 at 1.46.42 PM.png!
> Only the Ratis leader DataNode should verify ACL and block token
> -----------------------------------------------------------------
>
> Key: HDDS-9366
> URL: https://issues.apache.org/jira/browse/HDDS-9366
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Wei-Chiu Chuang
> Priority: Major
> Attachments: Screen Shot 2023-09-28 at 1.46.42 PM.png
>
>
> Today the DataNode perform ACL check and block token verification on each DataNodes.
>
> This is wrong, as DataNode can diverge in state. Only leader DN should decide to accept a request or not. I have seen a case where the follower reject a request because its block token expired, but the leader accepted the request. State diverged.
>
> cc: [~szetszwo] [~duongnguyen] [~ritesh]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org