[
https://issues.apache.org/jira/browse/HDDS-17871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated HDDS-17871:
-----------------------------------
Summary: Datanode gRPC connection holds back the tail of every
positioned-read reply (was: Datanode gRPC connection flips writability on
every positioned-read reply)
> Datanode gRPC connection holds back the tail of every positioned-read reply
> ---------------------------------------------------------------------------
>
> Key: HDDS-17871
> URL: https://issues.apache.org/jira/browse/HDDS-17871
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Affects Versions: 2.3.0
> Reporter: Sergey Soldatov
> Assignee: Sergey Soldatov
> Priority: Minor
>
> Netty's default write buffer limit for a connection is 64 KiB. One
> positioned-read reply is bigger than that: 64 KiB of data plus headers. So
> every reply the datanode sends marks the client connection as "not writable",
> and then "writable" again once the reply is sent.
> Each of these switches makes the datanode go through every stream open on
> that connection. With many concurrent reads on one connection, the datanode
> wastes event-loop time on this for every reply.
> We might set the child channels' WRITE_BUFFER_WATER_MARK to something bigger,
> so several concurrent replies fit below the low watermark.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]