[services] Backup - Pull Backup - Wait for the get reactor to terminate
ClosedPublic
Actions

Authored by • karol on Jun 23 2022, 4:13 AM.

Details

Reviewers

tomek

Commits

rCOMM5aa0124e6453: [services] Backup - Pull Backup - Wait for the get reactor to terminate

Summary

Depends on D4326

This is a bug fix which was spotted in https://phab.comm.dev/D4228#121209

The problem was, we didn't wait for the getReactor to gracefully terminate in the PullBackupReactor. The result was, if the client stopped working, the whole service crashed. Now it just shows an error and all objects are deleted properly.

Test Plan

Start pulling the backup and crash the client (you can probably use ctrl+c but I just used panic in rust) in the middle of receiving compaction chunks.

Diff Detail

Repository

rCOMM Comm

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

• karol created this revision.Jun 23 2022, 4:13 AM

Herald added subscribers: • abosh, atul, • adrian and 2 others. · View Herald TranscriptJun 23 2022, 4:13 AM

• karol edited the summary of this revision. (Show Details)Jun 23 2022, 4:16 AM

• karol edited the test plan for this revision. (Show Details)

• karol added a reviewer: tomek.

• karol added a parent revision: D4326: [services] Tests - Update backup test.

• karol mentioned this in D4228: [services] Tests - Add pull backup.

Harbormaster completed remote builds in B9915: Diff 13709.Jun 23 2022, 4:21 AM

• karol requested review of this revision.Jun 23 2022, 4:21 AM

tomek requested changes to this revision.Jun 27 2022, 5:52 AM

tomek added inline comments.

services/backup/src/Reactors/server/PullBackupReactor.cpp
183–185 ↗	(On Diff #13709)	Shouldn't we use `while` here or a second variant of `wait`- `void wait( std::unique_lock<std::mutex>& lock, Predicate stop_waiting );` https://en.cppreference.com/w/cpp/thread/condition_variable/wait to protect against a spurious wakeup?

This revision now requires changes to proceed.Jun 27 2022, 5:52 AM

• karol added a child revision: D4379: [services] Tests - Read port from the env vars.Jun 28 2022, 7:49 AM

• karol added inline comments.Jul 5 2022, 3:34 AM

services/backup/src/Reactors/server/PullBackupReactor.cpp
183–185 ↗	(On Diff #13709)	Discussed offline. We decided the best way to go will be to leave this as is but after a wake-up here we should check if the state is really `DONE`, because if it is not, then we should definitely throw an error. The thing is, people usually use a `while` loop for this: while (cond) { cv.wait(lock); } but I think we shouldn't do that because we call `notify_one` only once in the done callback. So if it's called twice (not sure how that could happen) or it is called before the state is set to `DONE` (this either) then it means that something went terribly wrong and we should definitely throw.