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

Resolve a problem with updated "put" key-value pairs #3206

Merged
merged 1 commit into from
Dec 1, 2023

Commits on Dec 1, 2023

  1. Resolve a problem with updated "put" key-value pairs

    Correctly retrieve updated "put" keys. In this release series,
    the mechanism for executing "refresh" is done by direct modex,
    which while inefficient does at least retrieve the data. In
    order for it to work with refresh, we have to pass the key
    to the remove daemon so it can specifically retrieve it.
    
    Not sure why the updated data isn't included in the "fence"
    that is being executed after the values have been changed.
    Nor why the insertion of a "group construct" call before
    updating the values should have any impact on the operation
    as the two are completely orthogonal.
    
    However, I do note that simply disabling the dstore resolves
    all observed problems. So I suspect we are again running up
    against the limitations of that subsystem.
    
    Note: this change requires a corresponding change on the
    host server's handling of the direct modex request.
    
    Signed-off-by: Ralph Castain <rhc@pmix.org>
    rhc54 committed Dec 1, 2023
    Configuration menu
    Copy the full SHA
    d7348c1 View commit details
    Browse the repository at this point in the history