[
https://issues.apache.org/jira/browse/HDFS-12329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167302#comment-16167302
]
Weiwei Yang commented on HDFS-12329:
------------------------------------
I see, SCM node manager has some lag on reporting DN states, check the state
from datanode side makes sense in this case. I am +1 on the v2 patch. 2 minor
comments on the logging,
LOG.info("sendCommand {} {}", isReadOnlyRequest, request);
>>
LOG.debug("sendCommand: {}, read only requst: {}", request, isReadOnlyRequest);
LOG.info("reply {} {}", isReadOnlyRequest, reply);
>>
LOG.debug("reply: {}, read only request: {}", reply, isReadOnlyRequest);
Thanks
> Ozone: Ratis: Readonly calls in XceiverClientRatis should use sendReadOnly
> --------------------------------------------------------------------------
>
> Key: HDFS-12329
> URL: https://issues.apache.org/jira/browse/HDFS-12329
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Labels: OzonePostMerge
> Fix For: HDFS-7240
>
> Attachments: HDFS-12329-HDFS-7240.001.patch,
> HDFS-12329-HDFS-7240.002.patch
>
>
> Currently both write and readonly calls in Ratis use RaftClient.send which
> enqueues the the request to the raft log and is processed later when the log
> entry is consumed.
> Readonly call can be optimized by using RaftClient.sendReadOnly which will
> directly query the RaftServer for a particular request.
> This jira will be used to discuss this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
