pika_migrate 处理v3.4示例同步异常

[chenbt-hz]

Is this a regression?

Yes

Description

代码版本：

https://github.com/OpenAtomFoundation/pikiwidb/tree/v3.5.6/tools/pika_migrate

参考步骤：

公众号文章 https://mp.weixin.qq.com/s/e3qtQwc5Vv1Ro4zaiC0CXw

从 v3.4 同步到 v3.5.6：

1.写入时报错：broken pipe —— 备注：添加定时ping以后基本解决

W1124 11:01:04.186374 30984 redis_sender.cc:157] RedisSender 8fails to send redis command *3
$3
SET
$11
test_key_30
$8
value_30
, times: 1, error: IO error: write error Broken pipe

从 v3.4 同步到 v4.0.2时：

1.工具的Master连接状态异常

【pika_migrate状态 —— 无法连接】redis-cli -p 9221 info Replication
# Replication(SLAVE)
role:slave
ReplicationID:
master_host: ***
master_port: ***
master_link_status:down
repl_connect_status:
db0:no_connect
slave_priority:100
slave_read_only:1
db_repl_state:(db0:NoConnect)
is_eligible_for_master_election:true
db0:binlog_offset=0 861738,safety_purge=none
slave_repl_offset:861738

【pika_migrate状态 —— 同步过程中失败】 —— 备注：migrate工具的binlogfile大小限制必须和master保持一致，否则会出现offset 、filenumber无法对齐
# Replication(SLAVE)
role:slave
master_host:***
master_port:***
master_link_status:down
slave_priority:100
slave_read_only:1
db_repl_error_state:(db0:Error)
db0 binlog_offset=1 45778,safety_purge=none

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)

Anything else?

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: pika_migrate handles v3.4 sample synchronization exceptions

[touis000]

写入时报错：broken pipe
这个应该目标库的timeout设置太短，默认是60S，空闲断开了。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Error when writing: broken pipe
This should be because the timeout setting of the target library is too short, the default is 60S, and it is disconnected when idle.

[touis000]

所以可以目标库的timeout参数设长一些。
或者pika_migrate加入重连机制或加多keeplive机制。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Therefore, the timeout parameter of the target library can be set longer.
Or pika_migrate adds a reconnection mechanism or adds a keeplive mechanism.

[touis000]

我去目标库去查报错的key，发现是能同步到目标库的。所以它应该是有重连机制的。
虽然有报错，其实成功写入目标库的。
我将目标库的timeout参数设置为1800S，就没有再出现这个报错了。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I went to the target database to check the error key and found that it could be synchronized to the target database. So it should have a reconnection mechanism.
Although there is an error, it is actually successfully written to the target library.
I set the timeout parameter of the target library to 1800S, and this error no longer appears.

[chenbt-hz]

所以可以目标库的timeout参数设长一些。 或者pika_migrate加入重连机制或加多keeplive机制。

是的，我加了个重连。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Therefore, the timeout parameter of the target library can be set longer. Or pika_migrate adds a reconnection mechanism or adds a keeplive mechanism.

Yes, I added a reconnection.