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

Do not create any instance manager pods for v2 volumes if one is already existing #2756

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

derekbit
Copy link
Member

Which issue(s) this PR fixes:

longhorn/longhorn#8456

What this PR does / why we need it:

An extra instance manager pod for v2 data engine requires an additional CPU core and 2 GiB of memory. If the resources are insufficient, the instance manager pod will be recreated and retried. To minimize unnecessary retries, do not create any new instance manager pods if one is already running.

Special notes for your reviewer:

Additional documentation or context

@derekbit
Copy link
Member Author

Ping @shuo-wu @mantissahz @c3y1huang @innobead for review. Thank you.

@derekbit
Copy link
Member Author

Updated and ready for review.
cc @shuo-wu @c3y1huang @innobead

@derekbit
Copy link
Member Author

derekbit commented Jul 1, 2024

@c3y1huang Can you help review the PR? Thank you.

…mes if one is already existing

An extra instance manager pod for v2 data engine requires an additional CPU core and 2 GiB of memory.
If the resources are insufficient, the instance manager pod will be recreated and retried.
To minimize unnecessary retries, do not create any new instance manager pods if one is already running.

Longhorn 8456

Signed-off-by: Derek Su <derek.su@suse.com>
@derekbit derekbit merged commit 9f187a3 into longhorn:master Jul 3, 2024
6 checks passed
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.

2 participants