Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Log disruptive commands / major nemesis steps in db nodes logs #10051

Open
soyacz opened this issue Feb 12, 2025 · 0 comments
Open

Log disruptive commands / major nemesis steps in db nodes logs #10051

soyacz opened this issue Feb 12, 2025 · 0 comments
Assignees
@soyacz @dimakr

Comments

@soyacz
Copy link
Contributor

soyacz commented Feb 12, 2025

In db logs we mark start and stop nemesis.
Would be useful to also mark disruption commands that happen on specific node as close as possible to actual disruption trigger. Things like:

  1. trigger stop/reboot node
  2. trigger decommission abort
  3. start reaching enospc
  4. abort repair
  5. disrupt_memory_stress
  6. stop compactions from CompactionOps

refs: #10018 (comment)
@soyacz soyacz mentioned this issue Feb 12, 2025
Merged
3 tasks
@fruch fruch changed the title Log disruptive commands in db nodes logs Log disruptive commands / major nemesis steps in db nodes logs Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@soyacz soyacz

@dimakr dimakr

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@soyacz @dimakr