apache/dubbo

[Proposal] Refactor the writeQueue in Triple, use tcp channel for flush

Open

#11,929 opened on Mar 26, 2023

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Java (26,453 forks)batch import
help wantedtype/proposal

Repository metrics

Stars
 (41,524 stars)
PR merge metrics
 (Avg merge 7d 14h) (20 merged PRs in 30d)

Description

In the current triple protocol, writeQueue is used to encapsulate frames and perform batch operations on io. However, since we use the http2 stream channel provided by netty, we cannot simply use the parent channel for flushing, which introduces quite a lot of complexity. Spend. We hope to be able to directly use the parent channel, which is the Tcp channel, to perform the flush operation

Contributor guide

Research direction
Investigate the current writeQueue implementation in Triple protocol and understand how netty's channel flushing works. Trace the flush path from the parent channel to determine how to replace the writeQueue with direct tcp channel flush.
Tech stack
java
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35