ob升级检查脚本报错和observer日志报错‘log sync timeout on leader'

OceanBase 技术问题
#1

【 使用环境 】 测试环境
【 OB or 其他组件 】OB
【 使用版本 】4.2.5.1
【问题描述】测试环境需要升级小版本从4251升级到4252 ，使用ob自带的升级检查脚本upgrade_checker.py执行时报错，报错如下图，且ob运行日志伴随大量报错‘log sync timeout on leader’

image
image1620×600 145 KB

image
image1750×784 102 KB

image
image2123×462 134 KB

后续问题复现时按照https://ask.oceanbase.com/t/topic/35602971/14?_gl=11p0wxuw_gaNzg2ODUyMzMxLjE3MjM2MjQ5MTk._ga_T35KTM57DZ*MTc0NTgyMjg3OS4zMS4xLjE3NDU4MjI5MjcuMTIuMC4w 此社区单子做了排查，未发现相同问题，具体排查记录如下：

企业微信截图_1745837791196
企业微信截图_17458377911961777×910 94.8 KB

image
image1609×840 63 KB

image
image1366×586 85.3 KB

image
image1341×490 167 KB

通过这次排查，确认了以下几个点：
1、问题发生时，/data/log1 磁盘空间足够使用，磁盘利用率并未打满，且磁盘是nv ssd性能足够；
2、事务响应时间，事务日志数和事务日志量并未看到异常情况；
3、memstore整体使用均衡，并未看到某个租户memstore 使用频繁。
4、相关参数如writing_throttling_trigger_percentage ，各个租户的设置不同，但是都在60%~90% 这个区间。

当前问题需求，希望排查出导致此问题的具体原因和解决当前升级检查报错问题，让我们顺利升级observer版本。

【复现路径】问题出现前后相关操作
【附件及日志】推荐使用OceanBase敏捷诊断工具obdiag收集诊断信息,详情参见链接（右键跳转查看）：

【SOP系列 22 】——故障诊断第一步(自助诊断和诊断信息收集)

【备注】基于 LLM 和开源文档 RAG 的论坛小助手已开放测试，在发帖时输入 [@论坛小助手] 即可召唤小助手，欢迎试用！

#3

根因分析场景: 针对卡合并场景的根因分析
根因分析命令: obdiag rca run --scene=major_hold
日志采集场景: 合并问题
日志采集命令: obdiag gather scene run --scene=observer.compaction

推荐使用 obdiag 工具进行根因分析和日志采集，以便确认问题所在。通过上述命令可以收集到与合并问题相关的日志，并分析可能引发 ‘log sync timeout on leader’ 错误的根本原因。

请您执行以上命令后，将生成的日志压缩包提供给我们，以便进一步排查问题。

另外，为了更好地帮助您解决问题，在此需要您提供一些额外的信息：

  1. 升级检查脚本 upgrade_checker.py 报错的具体错误信息是什么？
  2. 当前集群的版本号是多少？
  3. 是否有主备库配置？如果有，请问主备库之间是否存在延迟？
  4. 出现 ‘log sync timeout on leader’ 错误的时间点是否固定，还是随机发生？
  5. 集群当前的负载情况如何？是否有大事务或高并发操作？

附上敏捷诊断工具 obdiag 使用帮助链接

1 个赞
#4

查一下这两个信息
select * from __all_virtual_transfer_task\G;

SELECT * FROM DBA_OB_TENANT_JOBS WHERE JOB_TYPE = “ALTER_TENANT_LOCALITY” ORDER BY START_TIME DESC

日志upgrade_checker.log提供一下

1 个赞
#5

好的，这两个SQL待问题复现时，我会查询并提供给，关于upgrade_checker.log，这个需要提供完整文档版吗？因为上面是有个错误截图 的

image
image1750×784 102 KB

1 个赞
#6

根据您提供的 upgrade_checker.py 的错误日志，可以明确以下几点信息：

  1. 升级检查脚本报错原因
    错误信息显示：upgrade checker failed with 1 reasons: [212 replicas ynsyng, please check]。
    这表明在执行升级检查时，发现有 212 个副本（replicas）处于非同步状态（ynsyng）。

    在 OceanBase 数据库中，副本的同步状态非常重要。如果某些副本未能与主副本保持同步，可能会导致数据一致性问题或升级失败。

  2. 解决升级检查报错的步骤
    针对上述问题，您可以按照以下步骤进行排查和修复：

    • 确认副本同步状态
      使用以下 SQL 查询集群中所有副本的状态，找出哪些副本处于非同步状态：

      SELECT * FROM __all_virtual_clog_stat WHERE role = 2 AND is_in_sync = 0;

      其中：

      • role = 2 表示该副本是备副本。
      • is_in_sync = 0 表示该副本未与主副本同步。

    • 检查网络延迟或分区问题
      如果发现某些副本未同步，可能是由于网络延迟或分区问题导致的。请检查相关服务器之间的网络连接是否正常，并确保没有防火墙或其他网络限制影响副本间的通信。

    • 手动修复副本同步
      如果确认网络无问题但仍有副本未同步，可以尝试手动触发同步操作。具体方法如下：

      ALTER SYSTEM REBALANCE UNIT;

      或者针对特定租户触发同步：

      ALTER TENANT <tenant_name> REBALANCE UNIT;

    • 等待同步完成
      副本同步可能需要一定时间，请耐心等待并再次运行升级检查脚本，直到所有副本都处于同步状态。

  3. 关于 ‘log sync timeout on leader’ 报错
    根据您提供的 observer 日志，大量出现 log sync timeout on leader 的错误提示，这通常与以下几种情况有关：

    • 磁盘性能问题
      如果磁盘性能不足，可能导致日志写入速度过慢，从而引发超时。建议检查磁盘性能指标（如 IOPS 和延迟），并确保使用高性能的 NVMe SSD。

    • 高负载或大事务
      如果集群当前负载过高或存在大事务，可能会导致日志同步超时。可以通过以下 SQL 查询当前的事务和负载情况：

      SELECT * FROM gv$transaction WHERE status != 'INACTIVE';

    • 网络问题
      如果主从节点之间的网络延迟较高，也可能导致日志同步超时。建议检查网络延迟，并确保主从节点之间的带宽充足。

  4. 是否需要提供完整版 upgrade_checker.log
    如果您希望我们更深入地分析升级检查脚本的具体执行过程，建议提供完整的 upgrade_checker.log 文件。不过，从目前的截图来看，已经能够定位到主要问题（即 212 个副本未同步），因此您可以先按照上述步骤解决问题后再决定是否提供完整日志。

  5. 后续建议

    • 在问题解决后，重新运行升级检查脚本以确认所有检查项通过：
      python upgrade_checker.py -h <host> -P <port> -u <user> -p <password>
    • 如果问题仍然存在，请使用 obdiag 工具收集更多诊断信息，并将生成的日志压缩包提供给我们进一步分析。

如果您还有其他疑问或需要进一步帮助，请随时告知！

检索到的文档如下:

  1. 使用命令行进行运维
  2. 0001 ~ 3999
  3. 4000 ~ 4499

(小助手的答复已结束，如未能解决您的问题，请继续提问并等待其他同学的回复，谢谢！)

1 个赞
#7

upgrade_checker.log 这个日志提供完整版 方便排查问题 上面的语句别忘了查询

1 个赞
#8

好的

1 个赞
#9

image
image1172×274 36.5 KB

1 个赞
#10

[2025-04-28 21:04:46] INFO upgrade_checker.py:743 parameters from cmd: host=“127.0.0.1”, port=2881, user=“root@sys”, password="", timeout=“0”, log-file=“upgrade_checker.log”
[2025-04-28 21:04:46] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:46] INFO upgrade_checker.py:337 check observer version success, version = 4.2.5.1
[2025-04-28 21:04:46] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:47] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from oceanbase.__all_virtual_tenant_parameter_info where name=‘compatible’, rowcount = 1
[2025-04-28 21:04:47] INFO upgrade_checker.py:57 succeed to execute query: select count() from oceanbase.__all_tenant, rowcount = 1
[2025-04-28 21:04:50] INFO upgrade_checker.py:57 succeed to execute query: select count() from __all_virtual_core_table where column_name in (‘target_data_version’, ‘current_data_version’) and column_value = 17180001537, rowcount = 1
[2025-04-28 21:04:50] INFO upgrade_checker.py:387 check data version success, all tenant’s compatible/target_data_version/current_data_version is 4.2.5.1
[2025-04-28 21:04:50] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as unsync_cnt from GV$OB_LOG_STAT where in_sync = ‘NO’, rowcount = 1
[2025-04-28 21:04:50] INFO upgrade_checker.py:396 check paxos replica success
[2025-04-28 21:04:50] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from DBA_OB_TENANT_JOBS where job_status=‘INPROGRESS’ and result_code is null, rowcount = 1
[2025-04-28 21:04:52] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as rebalance_task_cnt from CDB_OB_LS_REPLICA_TASKS, rowcount = 1
[2025-04-28 21:04:52] INFO upgrade_checker.py:408 check rebalance task success
[2025-04-28 21:04:52] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_MAJOR_COMPACTION where (GLOBAL_BROADCAST_SCN > LAST_SCN or STATUS != ‘IDLE’), rowcount = 1
[2025-04-28 21:04:52] INFO upgrade_checker.py:416 check cluster status success
[2025-04-28 21:04:52] INFO upgrade_checker.py:57 succeed to execute query: select count() as count from DBA_OB_TENANTS where status != ‘NORMAL’, rowcount = 1
[2025-04-28 21:04:52] INFO upgrade_checker.py:428 check tenant status success
[2025-04-28 21:04:53] INFO upgrade_checker.py:57 succeed to execute query: select count() as count from oceanbase.__all_virtual_tenant_info where tenant_role != ‘PRIMARY’ and tenant_role != ‘STANDBY’, rowcount = 1
[2025-04-28 21:04:53] INFO upgrade_checker.py:438 check tenant info success
[2025-04-28 21:04:53] INFO upgrade_checker.py:57 succeed to execute query: select count() from DBA_OB_TENANTS where LOCKED = ‘YES’, rowcount = 1
[2025-04-28 21:04:53] INFO upgrade_checker.py:447 check tenant lock status success
[2025-04-28 21:04:53] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_RESTORE_PROGRESS, rowcount = 1
[2025-04-28 21:04:53] INFO upgrade_checker.py:456 check restore job success
[2025-04-28 21:04:54] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:55] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from __all_virtual_ddl_task_status, rowcount = 1
[2025-04-28 21:04:55] INFO upgrade_checker.py:502 check ddl task execut status success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_BACKUP_JOBS, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:513 check backup job success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select count() from oceanbase.__all_server where (start_service_time <= 0 or status != “active”), rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:592 check observer status success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select if (a.cnt = b.cnt, 1, 0) as passed from (select count() as cnt from oceanbase.__all_virtual_server_schema_info where refreshed_schema_version > 1 and refreshed_schema_vers
ion % 8 = 0) as a join (select count() as cnt from oceanbase.__all_server join oceanbase.__all_tenant) as b, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:599 check schema status success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select distinct(substring_index(build_version, ‘_’, 1)) from __all_server, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:585 check server version success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select tenant_name from oceanbase.DBA_OB_TENANTS, rowcount = 161
[2025-04-28 21:04:56] INFO upgrade_checker.py:609 check special tenant name success
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-04-28 21:04:56] INFO upgrade_checker.py:57 succeed to execute query: select tenant_id from oceanbase.__all_tenant where compatibility_mode = 1, rowcount = 0
[2025-04-28 21:04:56] INFO upgrade_checker.py:661 check oracle standby_replication privs success
[2025-04-28 21:04:57] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from oceanbase.__all_virtual_tenant_parameter_info where (name like “log_transport_compress_func” and value like “zlib_1.0”), rowcount = 1
[2025-04-28 21:04:57] INFO upgrade_checker.py:615 check log_transport_compress_func success
[2025-04-28 21:05:00] INFO upgrade_checker.py:57 succeed to execute query: select /*+ query_timeout(1000000000) */ count(1) from __all_virtual_table where (compress_func_name like ‘%zlib%’), rowcount = 1
[2025-04-28 21:05:00] INFO upgrade_checker.py:621 check table compression method success
[2025-04-28 21:05:00] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from GV$OB_PARAMETERS where (name like “tableapi_transport_compress_func” and value like “zlib%”);, rowcount = 1
[2025-04-28 21:05:00] INFO upgrade_checker.py:627 check table_api_transport_compress_func success
[2025-04-28 21:05:00] ERROR upgrade_checker.py:712 run error
Traceback (most recent call last):
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [11 replicas unsync, please check] ’
[2025-04-28 21:05:00] ERROR upgrade_checker.py:721 normal error
Traceback (most recent call last):
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [11 replicas unsync, please check] ’
[2025-04-28 21:05:00] ERROR upgrade_checker.py:749 normal error
Traceback (most recent call last):
File “upgrade_checker.py”, line 744, in
do_check(host, port, user, password, timeout, upgrade_params)
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [11 replicas unsync, please check] ’

1 个赞
#11

今天有空麻烦看下这个问题

1 个赞
#12

同步日志头超时？看不大明白

#13

你在执行一下 升级检查的脚本 再把日志重新发一下

#14

[2025-05-06 11:01:21] INFO upgrade_checker.py:743 parameters from cmd: host=“127.0.0.1”, port=2881, user=“root@sys”, password="", timeout=“0”, log-file=“upgrade_checker.log”
[2025-05-06 11:01:21] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:21] INFO upgrade_checker.py:337 check observer version success, version = 4.2.5.1
[2025-05-06 11:01:21] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:22] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from oceanbase.__all_virtual_tenant_parameter_info where name=‘compatible’, rowcount = 1
[2025-05-06 11:01:22] INFO upgrade_checker.py:57 succeed to execute query: select count() from oceanbase.__all_tenant, rowcount = 1
[2025-05-06 11:01:24] INFO upgrade_checker.py:57 succeed to execute query: select count() from __all_virtual_core_table where column_name in (‘target_data_version’, ‘current_data_version’) and column_value = 17180001537, rowco
unt = 1
[2025-05-06 11:01:24] INFO upgrade_checker.py:387 check data version success, all tenant’s compatible/target_data_version/current_data_version is 4.2.5.1
[2025-05-06 11:01:24] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as unsync_cnt from GV$OB_LOG_STAT where in_sync = ‘NO’, rowcount = 1
[2025-05-06 11:01:24] INFO upgrade_checker.py:396 check paxos replica success
[2025-05-06 11:01:24] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from DBA_OB_TENANT_JOBS where job_status=‘INPROGRESS’ and result_code is null, rowcount = 1
[2025-05-06 11:01:25] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as rebalance_task_cnt from CDB_OB_LS_REPLICA_TASKS, rowcount = 1
[2025-05-06 11:01:25] INFO upgrade_checker.py:408 check rebalance task success
[2025-05-06 11:01:25] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_MAJOR_COMPACTION where (GLOBAL_BROADCAST_SCN > LAST_SCN or STATUS != ‘IDLE’), rowcount = 1
[2025-05-06 11:01:25] INFO upgrade_checker.py:416 check cluster status success
[2025-05-06 11:01:25] INFO upgrade_checker.py:57 succeed to execute query: select count() as count from DBA_OB_TENANTS where status != ‘NORMAL’, rowcount = 1
[2025-05-06 11:01:25] INFO upgrade_checker.py:428 check tenant status success
[2025-05-06 11:01:26] INFO upgrade_checker.py:57 succeed to execute query: select count() as count from oceanbase.__all_virtual_tenant_info where tenant_role != ‘PRIMARY’ and tenant_role != ‘STANDBY’, rowcount = 1
[2025-05-06 11:01:26] INFO upgrade_checker.py:438 check tenant info success
[2025-05-06 11:01:26] INFO upgrade_checker.py:57 succeed to execute query: select count() from DBA_OB_TENANTS where LOCKED = ‘YES’, rowcount = 1
[2025-05-06 11:01:26] INFO upgrade_checker.py:447 check tenant lock status success
[2025-05-06 11:01:27] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_RESTORE_PROGRESS, rowcount = 1
[2025-05-06 11:01:27] INFO upgrade_checker.py:456 check restore job success
[2025-05-06 11:01:27] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:27] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from __all_virtual_ddl_task_status, rowcount = 1
[2025-05-06 11:01:27] INFO upgrade_checker.py:502 check ddl task execut status success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select count(1) from CDB_OB_BACKUP_JOBS, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:513 check backup job success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select count() from oceanbase.__all_server where (start_service_time <= 0 or status != “active”), rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:592 check observer status success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select if (a.cnt = b.cnt, 1, 0) as passed from (select count() as cnt from oceanbase.__all_virtual_server_schema_info where refreshed_schema_version >
1 and refreshed_schema_version % 8 = 0) as a join (select count() as cnt from oceanbase.__all_server join oceanbase.__all_tenant) as b, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:599 check schema status success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select distinct(substring_index(build_version, ‘_’, 1)) from __all_server, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:585 check server version success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select tenant_name from oceanbase.DBA_OB_TENANTS, rowcount = 161
[2025-05-06 11:01:28] INFO upgrade_checker.py:609 check special tenant name success
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select distinct value from GV$OB_PARAMETERS where name=‘min_observer_version’, rowcount = 1
[2025-05-06 11:01:28] INFO upgrade_checker.py:57 succeed to execute query: select tenant_id from oceanbase.__all_tenant where compatibility_mode = 1, rowcount = 0
[2025-05-06 11:01:28] INFO upgrade_checker.py:661 check oracle standby_replication privs success
[2025-05-06 11:01:29] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from oceanbase.__all_virtual_tenant_parameter_info where (name like “log_transport_compress_func” and value like “zlib_1.0”), row
count = 1
[2025-05-06 11:01:29] INFO upgrade_checker.py:615 check log_transport_compress_func success
[2025-05-06 11:01:30] INFO upgrade_checker.py:57 succeed to execute query: select /*+ query_timeout(1000000000) */ count(1) from __all_virtual_table where (compress_func_name like ‘%zlib%’), rowcount = 1
[2025-05-06 11:01:30] INFO upgrade_checker.py:621 check table compression method success
[2025-05-06 11:01:30] INFO upgrade_checker.py:57 succeed to execute query: select count(1) as cnt from GV$OB_PARAMETERS where (name like “tableapi_transport_compress_func” and value like “zlib%”);, rowcount = 1
[2025-05-06 11:01:30] INFO upgrade_checker.py:627 check table_api_transport_compress_func success
[2025-05-06 11:01:30] ERROR upgrade_checker.py:712 run error
Traceback (most recent call last):
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [30 replicas unsync, please check] ’
[2025-05-06 11:01:30] ERROR upgrade_checker.py:721 normal error
Traceback (most recent call last):
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [30 replicas unsync, please check] ’
[2025-05-06 11:01:30] ERROR upgrade_checker.py:749 normal error
Traceback (most recent call last):
File “upgrade_checker.py”, line 744, in
do_check(host, port, user, password, timeout, upgrade_params)
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
MyError: 'upgrade checker failed with 1 reasons: [30 replicas unsync, please check] ’
Traceback (most recent call last):
File “upgrade_checker.py”, line 744, in
do_check(host, port, user, password, timeout, upgrade_params)
File “upgrade_checker.py”, line 709, in do_check
check_fail_list()
File “upgrade_checker.py”, line 666, in check_fail_list
raise MyError(error_msg)
main.MyError: 'upgrade checker failed with 1 reasons: [30 replicas unsync, please check] ’

#15

应该是语句执行失败了 导致的

#16

具体是什么失败,影响升级吗

#17

这个脚本应该是企业版的吧 社区版应该没有这个 社区版也不推荐这样使用 建议obd或者ocp升级

#18

是社区版,有的集群跑这个脚本没问题,升级前不用校验吗

#19

那OB运行日志频繁刷这个报错是什么原因呢？‘log sync timeout on leader’，这个是否会影响集群升级？对数据库有什么影响?

#20

obd和ocp升级 这个两个工具会去检查的 主要商业版和社区版 是两个分支 使用的方式不一样 你执行脚本 是会有问题的

#21

具体把日志信息提供一下 重新发一个帖子 方便跟踪