Conversation
…tion with server - Set APP_DATABASE__ALLOW_MIGRATE=false after Nacos load so worker never runs migrations - Wrap set_var in unsafe block for Rust 2024 edition compliance - Prevents server/worker both running Migrator::up and hanging on pg_advisory_lock
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
问题
server 与 worker 共用同一 Nacos 配置且均在启动时执行数据库迁移，会竞争
pg_advisory_lock，导致容器卡在run database migration无法启动。方案
仅在 worker 进程内，在加载 Nacos 后强制设置
APP_DATABASE__ALLOW_MIGRATE=false，确保 worker 永不执行迁移；server 仍按 Nacos 配置执行迁移。变更
crates/worker/src/main.rs: 在load_env_from_nacos之后std::env::set_var("APP_DATABASE__ALLOW_MIGRATE", "false")，并用unsafe块满足 Rust 2024 对set_var的要求。