lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(controller): wire real limits.yaml config through cluster_config

Browse source 
xcesched_push_configs() sent two hardcoded limit1/limits2 test
literals to the scheduler (behind a #if 0/FIXME "we use builtin limit
currently"), ignoring whatever was actually loaded from cluster_config.
Migrate those literals into limits.yaml as real entries and wire
conf4sched->nlimits/limits from c->myconf->cluster_config directly.

cluster_init_phase2 also downgrades its "cluster_config not loaded"
ERROR to INFO — a standby legitimately reaching phase2 before the
primary's config-push has delivered bytes yet is normal cold-boot
behavior, not a failure; it already matches load_primary_config's
INFO-level framing for the same condition.
This commit is contained in:
Rongsong Shen 2026-07-23 04:24:01 +00:00
parent 0649e17f62
commit 18e7a0e9e1
3 changed files with 45 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

9
src/controller/cluster.c
View file

@ -1303,7 +1303,14 @@ int cluster_init_phase2(cluster_t* c)
return -EINVAL;
if (c->myconf->cluster_config == NULL) {
ERROR("cluster_init_phase2: cluster_config not loaded");
/* Normal during cold boot: a standby reaches phase2 (post-election)
* before the primary's config-push has delivered bytes yet. Not a
* divergence or a hard failure — matches load_primary_config's own
* "will fetch from primary after election" INFO-level framing for
* the same underlying condition. The caller retries. */
INFO("cluster_init_phase2: cluster_config not loaded yet — normal "
"during cold boot while awaiting the primary's config-push; "
"will retry once it arrives");
return -EINVAL;
}