libkvs: add cache bypass option to kvs_checkpoint functions
#4476
Assignees
Comments
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 8, 2022
Problem: The kvs_checkpoint functions checkpoing data to the backing store through the broker's content-cache. There is no way to bypass the cache, similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Solution: Support a new KVS_CHECKPOINT_FLAG_CACHE_BYPASS, that will get/put directly to the backing store. The flag is very similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Fixes flux-framework#4476
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 8, 2022
Problem: The kvs_checkpoint functions checkpoint data to the backing store through the broker's content-cache. There is no way to bypass the cache, similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Solution: Support a new KVS_CHECKPOINT_FLAG_CACHE_BYPASS, that will get/put directly to the backing store. The flag is very similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Fixes flux-framework#4476
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 10, 2022
Problem: The kvs_checkpoint functions checkpoint data to the backing store through the broker's content-cache. There is no way to bypass the cache, similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Solution: Support a new KVS_CHECKPOINT_FLAG_CACHE_BYPASS, that will get/put directly to the backing store. The flag is very similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Fixes flux-framework#4476
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 10, 2022
Problem: The kvs_checkpoint functions checkpoint data to the backing store through the broker's content-cache. There is no way to bypass the cache, similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Solution: Support a new KVS_CHECKPOINT_FLAG_CACHE_BYPASS, that will get/put directly to the backing store. The flag is very similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Fixes flux-framework#4476
chu11
added a commit
to chu11/flux-core
that referenced
this issue
Aug 10, 2022
Problem: The kvs_checkpoint functions checkpoint data to the backing store through the broker's content-cache. There is no way to bypass the cache, similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Solution: Support a new KVS_CHECKPOINT_FLAG_CACHE_BYPASS, that will get/put directly to the backing store. The flag is very similar to libcontent's CONTENT_FLAG_CACHE_BYPASS flag. Fixes flux-framework#4476
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per discussion in #4463, it would be nice to add a cache bypass option to the
kvs_checkpointfunctions. It can be used in dump/restore to go directly to the backing store as well.The text was updated successfully, but these errors were encountered: