resource.scheduling key should only be used on rank 0 if possible #6480
Comments
grondo
added a commit
to grondo/flux-core
that referenced
this issue
Dec 5, 2024
Problem: The Rv1 scheduling key as JGF can be large and time-consuming to generate and distribute, but currently it is required on all nodes. Since the key is really only used by the scheduler on rank 0, it would be ideal resource.scheduling was only read on rank 0. Only process the resource.scheduling config key on rank 0. Fixes flux-framework#6480
grondo
added a commit
to grondo/flux-core
that referenced
this issue
Dec 5, 2024
Problem: The Rv1 scheduling key as JGF can be large and time-consuming to generate and distribute, but currently it is required on all nodes. Since the key is really only used by the scheduler on rank 0, it would be ideal if resource.scheduling was only read on rank 0. Only process the resource.scheduling config key on rank 0. Fixes flux-framework#6480
grondo
added a commit
to grondo/flux-core
that referenced
this issue
Dec 6, 2024
Problem: The Rv1 scheduling key as JGF can be large and time-consuming to generate and distribute, but currently it is required on all nodes. Since the key is really only used by the scheduler on rank 0, it would be ideal if resource.scheduling was only read on rank 0. Only process the resource.scheduling config key on rank 0. Fixes flux-framework#6480
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem: The Rv1
schedulingkey as JGF can be large and time-consuming to generate and distribute, but currently it is required on all nodes. Since the key is really only used by the scheduler on rank 0, it would be idealresource.schedulingwas only read on rank 0.The text was updated successfully, but these errors were encountered: