kvs: remove fence support #6587
Assignees
Comments
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Jan 30, 2025
Problem: The KVS fence implementation is virtually unused. It also has the potential for denial-of-service attacks. Its implementation is also quite "one off" within the KVS, limiting some ability to refactor the code. For all these reasons, it should be removed. If fence-like behavior is ever needed again in the future, it should be implemented as a stand alone module on top of the KVS. Solution: Remove all fence support in the KVS. Fixes flux-framework#6587
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Jan 30, 2025
Problem: The KVS fence implementation is virtually unused. It also has the potential for denial-of-service attacks. Its implementation is also quite "one off" within the KVS, limiting some ability to refactor the code. For all these reasons, it should be removed. If fence-like behavior is ever needed again in the future, it should be implemented as a stand alone module/service on top of the KVS. Solution: Remove all fence support in the KVS. Fixes flux-framework#6587
This was referenced Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per discussion in #6112, the only use of the KVS fence is a non-default (and seemingly unused) option in the shell PMI plugin.
Removal of the KVS fence support could lead to a lot of cleanup in the KVS, most notably the transaction code is effectively no longer needed, since all transactions will be from a single request.
#6112 would be closed as a result
Lets give it a shot :-)
The text was updated successfully, but these errors were encountered: