Skip to content

fix: legacy job compatibility for replication_num - #658

Merged
w41ter merged 2 commits into
selectdb:devfrom
Ryan19929:fix-helper
Dec 17, 2025
Merged

w41ter merged 2 commits into
selectdb:devfrom
Ryan19929:fix-helper

Conversation

@Ryan19929

Copy link
Copy Markdown
Contributor

No description provided.

@Ryan19929

Copy link
Copy Markdown
Contributor Author

@w41ter 忘记把helper加进来了,现在补上

@Ryan19929 Ryan19929 changed the title Add helper method to create CCR job with custom replication number fix: legacy job compatibility for replication_num Dec 8, 2025
@Ryan19929

Copy link
Copy Markdown
Contributor Author

@w41ter#649 我之前的pr没有处理recover老任务属性,如果老任务重新触发全量同步,传入的replication_num的的值会变成0(这是一个非法值)。

@Ryan19929

Copy link
Copy Markdown
Contributor Author

如果没有处理旧任务,就会出现下面的错误。
[2025-12-08 17:35:05.977] WARN job sync failed, job: ccr_test, err: [normal] restore snapshot failed, status: TStatus({StatusCode:ANALYSIS_ ERROR ErrorMsgs:[errCode = 2, detailMessage = Replication num should between 1 and 32767, command: org.apache.doris.nereids.trees.plans.comm ands.RestoreCommand@2f77204f]})

@w41ter
w41ter merged commit 8bc8a20 into selectdb:dev Dec 17, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants