Skip to content

remote_cache: Kill SeaweedFS instead of stopping it - #285

Merged
daandemeyer merged 1 commit into
amutable-systems:mainfrom
daandemeyer:push-yuntlonxnynx
Oct 9, 2026
Merged

daandemeyer merged 1 commit into
amutable-systems:mainfrom
daandemeyer:push-yuntlonxnynx

Conversation

@daandemeyer

Copy link
Copy Markdown
Member

weed keeps running for more than a minute after SIGTERM, because its filer
retries a metadata write that fails once the volume server has stopped.
close() waits 30 seconds for weed to exit and then kills weed. Each of the two
test classes that start a server spends half a minute in that wait. Kill weed
right away. Every caller removes the server's directory afterwards.

Signed-off-by: Daan De Meyer daan@amutable.com

weed keeps running for more than a minute after SIGTERM, because its filer
retries a metadata write that fails once the volume server has stopped.
close() waits 30 seconds for weed to exit and then kills weed. Each of the two
test classes that start a server spends half a minute in that wait. Kill weed
right away. Every caller removes the server's directory afterwards.

Signed-off-by: Daan De Meyer <daan@amutable.com>

@martinpitt martinpitt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔫

@daandemeyer
daandemeyer merged commit 7d71e28 into amutable-systems:main Oct 9, 2026
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