node: Process killing by systemd #259
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#259
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expected Behavior
Current Behavior
Steps to Reproduce
rostfs-cli control set-status --status offline
frostfs-adm morph force-new-epoch
sudo systemctl stop frostfs-storage.service
Regression
Yes
We hit same issue on hardware deployment with just step 3
@abereziny could you add in test code one more call to pprof? I think somewhere near
systemctl status
.With this info it will be much easier to solve this issue:
@abereziny the idea is to stop in background and check status(with pprof) until service stopped
sudo systemctl stop frostfs-storage.service
is a sync call. After it returns control services is already failed.So if we wan't some info during this we should probably do
nohup sudo systemctl...
or something.I wasn't able to reproduce on clean cluster. This means that we need pre-filled cluster and I'm currently struggle to find free one.
Can it be related to asynchronous write-cache initialization? cc @carpawell
Related #362, #364, #366.
Routines list before killing by systemd in attachment.
I finally was able to gather pprof snapshots during process shutdown.
Closed by #362, #363, #364, #366, #379, #403, #404