Skip to content

Specify log file path in stellar-core.cfg for catch up worker - #192

Merged
sisuresh merged 1 commit into
mainfrom
log-path
Aug 15, 2024
Merged

sisuresh merged 1 commit into
mainfrom
log-path

Conversation

@jayz22

@jayz22 jayz22 commented Aug 15, 2024

Copy link
Copy Markdown
Contributor

No description provided.

@sisuresh
sisuresh merged commit 997992b into main Aug 15, 2024
@sisuresh
sisuresh deleted the log-path branch August 15, 2024 17:42
Jonathan-Eid added a commit to Jonathan-Eid/supercluster that referenced this pull request Aug 27, 2026
The reserve was subtracted from the idle pool alone, but `outstanding`
counts in-progress jobs too, and those already have a worker each. With
1000 workers, 700 busy and 700 jobs outstanding, the surplus came out as
300 - 700 and nothing was marked at all: 300 idle workers were held to
cover work that was already being served.

Counting the surplus against every unmarked worker gives 1000 - 700 = 300,
and those 300 idle workers are marked. Only idle workers are ever marked,
and the reserve still keeps `max outstanding minUnmarkedWorkers` workers
unmarked, so a requeued job still has somewhere to go -- an unmarked busy
worker becomes claimable as soon as it finishes.

Run stellar#192 never sat in that state: in-progress fell from 1022 to 80 in three
minutes, so the largest instantaneous gap was about 80 workers and
retirement was capped at 32 a pass throughout. A run whose ranges vary
enough for in-progress to decay gradually would sit there and mark nothing.
Jonathan-Eid added a commit to Jonathan-Eid/supercluster that referenced this pull request Aug 27, 2026
Per-worker StatefulSets renamed pods to <release>-stellar-core-<i>-0, so the
last hyphen-separated segment is the StatefulSet's own -0 suffix rather than
the worker index. Every metrics record in run stellar#192 reported core_id 0.

Nothing consumes the field -- the monitor discards it and keeps only the two
durations -- but a value that is always 0 reads as real data, so pass the
index the chart already has.
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