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

Release v0.1.2 #22

Merged
merged 2 commits into from
Aug 30, 2024
Merged

Release v0.1.2 #22

merged 2 commits into from
Aug 30, 2024

Conversation

matthew-richerson
Copy link

Release v0.1.2

bdevcich and others added 2 commits August 23, 2024 14:55
When more than 10 data movement requests come in for a particular
rabbit, the default sshd configuration starts dropping 30% of
connections and drops all after 100 connections (the default value is
set to 10:30:100). This causes data movement requests to fail since any
concurrency over 10 causes ssh to close connections (from mpirun).

This change increases that value to be able handle the max theoretical
load for a particular rabbit. This image runs on 1 pod per rabbit node
(i.e. nnf-dm-worker-*) and each rabbit node supports 16 compute nodes of
192 cores. Each core on a compute node could be creating a data movement
request.

16 * 192 = 3072

Bump it up to an power of 2 for good measure -> 4096.

Signed-off-by: Blake Devcich <[email protected]>
@matthew-richerson matthew-richerson merged commit 8cff6d7 into releases/v0 Aug 30, 2024
3 checks passed
@matthew-richerson matthew-richerson deleted the release-v0.1.2 branch August 30, 2024 20:01
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