You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2023/11/13 13:01:00 UTC
[jira] [Commented] (HDDS-9681) Allow OM to detect client address when using OM gRPC
[ https://issues.apache.org/jira/browse/HDDS-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785486#comment-17785486 ]
Attila Doroszlai commented on HDDS-9681:
----------------------------------------
Thanks [~Siberian Sky] for extracting this from HDDS-9651. Seems like [~vtutrinov] has been working on similar change for HDDS-9663 (just created the PR an hour ago).
> Allow OM to detect client address when using OM gRPC
> ----------------------------------------------------
>
> Key: HDDS-9681
> URL: https://issues.apache.org/jira/browse/HDDS-9681
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Kirill Sizov
> Priority: Major
>
> The RATIS object reading is currently implemented using a gRPC client (specifically, the {{BlockInputStream.getChunkInfos()}} method switches the pipeline type to {{STANDALONE}}, and the {{XceiverClientManager}} selects a gRPC client).
> Unfortunately, this configuration does not allow the Ozone Manager to determine the client's host address since the {{OmMetadatareader.getClientAddress()}} method only works for Hadoop RPC interactions. This failure to detect the client's address results in an empty {{nodesInOrder}} field in the response received by the client, causing the datanodes to be read in the default order in the pipeline, with the leader node being read first.
--
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