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

fix/vc-31703-agent-memory-startup-spikes #525

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

mol-george
Copy link
Contributor

@mol-george mol-george commented Mar 22, 2024

This attempts to fix the issue in VC-31703.

The initial data gatherer sync operation is currently executed async which might cause in an unreasonable amount of memory being used by the agent pod which results in the pod being OOM Killed.

Executing this operation one data gatherer at the time might mitigate this. Extending the time took for the initial sync is not a concern at this point.

@mol-george mol-george requested a review from tfadeyi March 22, 2024 09:59
@mol-george mol-george self-assigned this Mar 22, 2024
@mol-george mol-george merged commit c7a5b6b into master Mar 28, 2024
8 checks passed
@mol-george mol-george deleted the fix/vc-31703-agent-memory-startup-spikes-1 branch March 28, 2024 13:58
@@ -122,38 +123,32 @@ func Run(cmd *cobra.Command, args []string) {
log.Fatalf("failed to instantiate %q data gatherer %q: %v", kind, dgConfig.Name, err)
}

wg.Add(1)
Copy link
Member

Choose a reason for hiding this comment

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

Just passing by, quick questions: looks like the waitgroup isn't used anymore? Why has it been kept?

@maelvls
Copy link
Member

maelvls commented Jul 22, 2024

Passing by:

Update 9 Aug 2024: @wallrj has been working on improvements in #554.

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

Successfully merging this pull request may close these issues.

3 participants