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.

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

Cloud Storage: Ignore abort_requested_exception on shutdown #16780

Merged
merged 2 commits into from
Mar 1, 2024

Conversation

jcipar
Copy link
Contributor

@jcipar jcipar commented Feb 28, 2024

Looked like the partition was being moved and we were letting an abort error leak out.

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.3.x
  • v23.2.x
  • v23.1.x

Release Notes

  • none

Fixes: #16726

Fixes: #16635

@CLAassistant
Copy link

CLAassistant commented Feb 28, 2024

CLA assistant check
All committers have signed the CLA.

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Feb 28, 2024

andrwng
andrwng previously approved these changes Feb 29, 2024
Copy link
Contributor

@andrwng andrwng left a comment

Choose a reason for hiding this comment

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

Nice! A couple suggestions, though I don't feel too strongly about them.

Comment on lines 1271 to 1272
.handle_exception_type(
[](const ss::abort_requested_exception& /* ignore */) {})
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: it might be useful to still log these, but at debug log level. In digging into CI failures, silently dropped exceptions can be the difference between an obvious root cause or not (note that most CI runs with trace level logging enabled)

Copy link
Member

Choose a reason for hiding this comment

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

Ahh good point. I advised @jcipar to not log at all (based on ssx::background behavior) but I think you're right.

@@ -1268,6 +1268,8 @@ ss::future<upload_result> remote::delete_objects_sequentially(
results.push_back(result);
});
})
.handle_exception_type(
[](const ss::abort_requested_exception& /* ignore */) {})
.handle_exception_type([ctxlog](const std::exception& ex) {
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: it might not be an issue, but just fyi, check out ssx::is_shutdown_exception -- if other kinds of common shutdown-related errors pop up from this call site it might be worth switching over

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How does this change look?

Copy link
Contributor

Choose a reason for hiding this comment

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

This looks great! Thank you

@@ -1268,6 +1268,8 @@ ss::future<upload_result> remote::delete_objects_sequentially(
results.push_back(result);
});
})
.handle_exception_type(
[](const ss::abort_requested_exception& /* ignore */) {})
.handle_exception_type([ctxlog](const std::exception& ex) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks great! Thank you

Comment on lines +1274 to +1280
vlog(
ctxlog.debug,
"Failed to delete keys during shutdown: {}",
ex.what());

} else {
vlog(ctxlog.error, "Failed to delete keys: {}", ex.what());
Copy link
Contributor

Choose a reason for hiding this comment

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

this would be a good place for vlogl, eg

auto log_level = ...; 
vlogl(ctxlog, log_level, ...);

but the messages are different

@jcipar jcipar merged commit c03cf4b into dev Mar 1, 2024
16 checks passed
@jcipar jcipar deleted the jcipar/16726-bad-log-line branch March 1, 2024 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants