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

Comunicate and reflect main node state to other nodes #9556

Closed
JanKrivanek opened this issue Dec 16, 2023 · 0 comments
Closed

Comunicate and reflect main node state to other nodes #9556

JanKrivanek opened this issue Dec 16, 2023 · 0 comments
Labels
Area: Logging Area: Server needs-design Requires discussion with the dev team before attempting a fix. needs-triage Have yet to determine what bucket this goes in. performance

Comments

@JanKrivanek
Copy link
Member

Context

Today the env variables tweaks influence only the main node - other nodes (or the server) might not reflect those.
Similarly - logger subscriptions are not communicated anywhere - leading to all BuildEventArg events being emitted and transfered despite they mightnot be consumed at all.

We should transfer the state of env and subscriptions from main node to all other nodes and tweak processing accordingly.

Related

#9501
@JanKrivanek JanKrivanek added needs-design Requires discussion with the dev team before attempting a fix. performance Area: Logging needs-triage Have yet to determine what bucket this goes in. Area: Server labels Dec 16, 2023
@AR-May AR-May closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Logging Area: Server needs-design Requires discussion with the dev team before attempting a fix. needs-triage Have yet to determine what bucket this goes in. performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JanKrivanek @AR-May