You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a use case for being able to look up the flux session ranks that are running on a given hostname, e.g. the reverse of #892?
We disabled the population of resource-hwloc by_host by default in #716 for performance reasons that may have since been addressed by #732. One possibility is to re-enable that and add a nodeset key under it.
In order to write a nodeset, each rank would need to know its "clique ranks" which the broker already knows from its PMI bootstrap and could export in a broker attribute. With that information we could also have only the lowest numbered rank in the clique write the data.
The text was updated successfully, but these errors were encountered:
Is there a use case for being able to look up the flux session ranks that are running on a given hostname, e.g. the reverse of #892?
We disabled the population of resource-hwloc
by_host
by default in #716 for performance reasons that may have since been addressed by #732. One possibility is to re-enable that and add anodeset
key under it.In order to write a nodeset, each rank would need to know its "clique ranks" which the broker already knows from its PMI bootstrap and could export in a broker attribute. With that information we could also have only the lowest numbered rank in the clique write the data.
The text was updated successfully, but these errors were encountered: