Skip to content

Conversation

moogacs
Copy link
Member

@moogacs moogacs commented Aug 25, 2025

using kill is aggressive while we have 1 voter, it could cause corruption , instead use stop to guarantee graceful shutdown

1st run :using stop instead of kill https://github.com/weaviate/weaviate-chaos-engineering/actions/runs/17207908546
2nd run: using kill but instead mount volumes https://github.com/weaviate/weaviate-chaos-engineering/actions/runs/17208636414
3rd : similiar changes for 2nd run https://github.com/weaviate/weaviate-chaos-engineering/actions/runs/17208988882

Copy link

@orca-security-eu orca-security-eu bot left a comment

Choose a reason for hiding this comment

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

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed SAST high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

@moogacs moogacs changed the title fix(replication_tunable_consistency): use stop instead of kill fix(replication_tunable_consistency): persist volumes for single voters Aug 25, 2025
@weaviate-git-bot
Copy link

Great to see you again! Thanks for the contribution.

beep boop - the Weaviate bot 👋🤖

PS:
Are you already a member of the Weaviate Slack channel?

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.

3 participants