-
Notifications
You must be signed in to change notification settings - Fork 955
Introduce MPTCP for replica #1961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #1961 +/- ##
============================================
+ Coverage 70.99% 71.05% +0.06%
============================================
Files 123 123
Lines 65918 66040 +122
============================================
+ Hits 46798 46925 +127
+ Misses 19120 19115 -5
🚀 New features to boost your workflow:
|
|
@zuiderkwast @xbasel What do you think about the latest version? |
|
I haven't looked yet. We are working on patch releases now. I will take a look in a few days. |
zuiderkwast
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is mostly fine. I have only some minor comments.
Since commit 4a92db9("Introduce MPTCP (valkey-io#1811)"), valkey server starts to support MPTCP. Support MPTCP for replica as client side. Signed-off-by: zhenwei pi <[email protected]>
Signed-off-by: zhenwei pi <[email protected]>
Signed-off-by: zhenwei pi <[email protected]>
Signed-off-by: zhenwei pi <[email protected]>
|
Apply @zuiderkwast 's suggestions, force push a commit over 3 commits to fix DCO error. |
|
@valkey-io/core-team This is the follow-up of MTPCP to allow replication to use MPTCP. I think we already decided about this when we discussed and decided about MPTCP in the meeting some weeks ago. Please comment if you disagree. |
Signed-off-by: zhenwei pi <[email protected]>
Signed-off-by: zhenwei pi <[email protected]>
|
MPTCP is really good! |
Allow replicas to use MPTCP in the outgoing replication connection. A new yes/no config is introduced `repl-mptcp`, default `no`. For MPTCP to be used in replication, the primary needs to be configured with `mptcp yes` and the replica with `repl-mptcp yes`. Otherwise, the connection falls back to regular TCP. Follow-up of valkey-io#1811. --------- Signed-off-by: zhenwei pi <[email protected]>
Allow replicas to use MPTCP in the outgoing replication connection.
A new yes/no config is introduced
repl-mptcp, defaultno.For MPTCP to be used in replication, the primary needs to be configured with
mptcp yesand the replica withrepl-mptcp yes. Otherwise, the connection falls back to regular TCP.Follow-up of #1811.
Cc Linux kernel MPTCP maintainer @matttbe @geliangtang @Dwyane-Yan
Cc @xbasel