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

Worker Profiles - Active profile not being tracked #8516

Closed
Tracked by #8640
shreyas-gopalakrishna opened this issue Jun 29, 2022 · 0 comments · Fixed by #8763
Closed
Tracked by #8640

Worker Profiles - Active profile not being tracked #8516

shreyas-gopalakrishna opened this issue Jun 29, 2022 · 0 comments · Fixed by #8763

Comments

@shreyas-gopalakrishna
Copy link
Member

shreyas-gopalakrishna commented Jun 29, 2022

During specialization, we want to restart job host to use the right profile in case it has changed.
Currently active profiles and existing profiles are not visible at WebHostRpcWorkerChannelManager

Currently the profile manager is initialized at the RpcWorkerConfigFactory and also at WebHostRpcWorkerChannelManager.cs . Since both are instantiated in different contexts, they currently do not share the existing profiles and active profile information. We want to mainly have one copy/instance of the profile manager so we have consistent profiles data.

Since Job host is restarted multiple times, the profile manager is initialized multiple times. To avoid this it is decided to make the service itself a global application singleton by moving it to the Webhost.

Profiles PR - #8365

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.