Skip to content

logging: fix bug where links wouldn't be promptly activated #90826

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mjchen0
Copy link
Contributor

@mjchen0 mjchen0 commented May 29, 2025

The log process thread is what activates multidomain log links, but if all backends were already initialized, it would enter a mode where it would block until new local logs were ready to be processed, even if links were not yet completed in activation. Change the logic for computing the timeout used to block the processing thread so that it stays in periodic polling mode if there are still log links that haven't finished activating.

The log process thread is what activates multidomain log
links, but if all backends were already initialized,
it would enter a mode where it would block until new
local logs were ready to be processed, even if links
were not yet completed in activation. Change the logic
for computing the timeout used to block the processing
thread so that it stays in periodic polling mode if there
are still log links that haven't finished activating.

Signed-off-by: Mike J. Chen <[email protected]>
@mjchen0 mjchen0 force-pushed the log_core_activitation_polling branch from 16f5880 to 57d62ed Compare May 30, 2025 00:29
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants