fix: Remove BE caching mechanism and simplify replication number validation #651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
如果去掉缓存机制，那么每次执行前都需要获取一遍了，有更好的办法保证在避免缓存失效，同时减少获取 backend RPC 次数吗？ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
主要解决 CCR Syncer 无法自动检测 Doris 集群 BE 节点变化的问题，同时优化了相关代码结构。
问题
Meta 对象会缓存 Backend（BE）信息，只在首次调用时从 FE 获取，之后一直使用缓存
当 Doris 集群扩容时，CCR Syncer 无法感知到 BE 节点的变化
当syncer任务从增量转到全量同步时，ccr将不完整的backend信息发送给下游集群做restore
产生报错：failed to get remote be address of be: xxx
方案
删除 getBackend 缓存机制