-
Notifications
You must be signed in to change notification settings - Fork 0
Consider main channel client as replica #47
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 ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## cluster-asm #47 +/- ##
==============================================
Coverage ? 69.51%
==============================================
Files ? 125
Lines ? 73571
Branches ? 0
==============================================
Hits ? 51142
Misses ? 22429
Partials ? 0
🚀 New features to boost your workflow:
|
|
Hi @tezc after introducing task id, i think we can use task id to authenticate the rdb channel, i think it is better than client id, and consistent with CLUSTER SYNCSLOTS RANGE, WDYT? the commit is rdb channel uses task id to authenticate |
* dest as replica * add test cases * Fix test cases * rdb channel uses task id to authenticate * revert syncslots-reply * task id check * use task id to find status
* dest as replica * add test cases * Fix test cases * rdb channel uses task id to authenticate * revert syncslots-reply * task id check * use task id to find status
No description provided.