全量同步失败后，会直接跳过全量同步，主从复制状态会变为不需要全量同步的正常状态 #2433
Labels
☢️ Bug
Something isn't working
Comments
chengyu-l
pushed a commit
to chengyu-l/pika
that referenced
this issue
Mar 1, 2024
chengyu-l
pushed a commit
to chengyu-l/pika
that referenced
this issue
Mar 4, 2024
chengyu-l
pushed a commit
to chengyu-l/pika
that referenced
this issue
Mar 5, 2024
AlexStocks
pushed a commit
that referenced
this issue
Mar 6, 2024
…kipped directly(#2433) (#2439) Co-authored-by: liuchengyu <[email protected]>
luky116
pushed a commit
to luky116/pika
that referenced
this issue
Mar 14, 2024
…kipped directly(OpenAtomFoundation#2433) (OpenAtomFoundation#2439) Co-authored-by: liuchengyu <[email protected]>
luky116
pushed a commit
to luky116/pika
that referenced
this issue
Mar 14, 2024
…kipped directly(OpenAtomFoundation#2433) (OpenAtomFoundation#2439) Co-authored-by: liuchengyu <[email protected]>
luky116
pushed a commit
that referenced
this issue
Mar 18, 2024
…kipped directly(#2433) (#2439) Co-authored-by: liuchengyu <[email protected]>
bigdaronlee163
pushed a commit
to bigdaronlee163/pika
that referenced
this issue
Jun 8, 2024
…kipped directly(OpenAtomFoundation#2433) (OpenAtomFoundation#2439) Co-authored-by: liuchengyu <[email protected]>
cheniujh
pushed a commit
to cheniujh/pika
that referenced
this issue
Sep 24, 2024
…kipped directly(OpenAtomFoundation#2433) (OpenAtomFoundation#2439) Co-authored-by: liuchengyu <[email protected]>
cheniujh
pushed a commit
to cheniujh/pika
that referenced
this issue
Sep 24, 2024
…kipped directly(OpenAtomFoundation#2433) (OpenAtomFoundation#2439) Co-authored-by: liuchengyu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a regression?
Yes
Description
将 RsyncServerConn::HandleMetaRsyncRequest 代码逻辑稍微调整一下，如下图，模拟请求失败，下面的代码会在全量同步请求元数据时一直保持失败。
从下图中可以看出，从节点的主从复制状态从WaitDBSync变为Error，再到后来的正常状态（没有进行全量数据同步）
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: