Al Chu
Highly related but somewhat different to #6264 and #6265, we should define what the maximum value in the KVS is. It is nominally 2G - 1 b/c that is the...
Per discussion in #6256 > I wonder if it would be easier to implement a limit on storing a large value in the first place? > I hate to suggest...
Problem: Before checkpointing, users need to remember to call content.flush, to ensure data has been flushed to the backing store. It is easy to forget this. Within the content module,...
Problem: When the KVS module is unloaded, a checkpoint of the root reference is attempted. However, a content.flush is not done beforehand. This could result in an invalid checkpoint reference...
Problem: A backing store is required for content.flush but it is not required for content.checkpoint-put. This is inconsistent and can lead to checkpointing problems done the line. Require content.checkpoint-put to...
As noted in #6242, there appears to be an inconsitency in the content module - a `content.flush` will fail if a backing store is not loaded - a `content.checkpoint-put` will...
Per comment / idea in #6240 Pro: no need to require user to call before calling `content-checkpoint.put`. If backing store isn't loaded, the content module will know not to call...
This continues conversation from PR #6217. From @garlick > After consulting with @kkier a bit on this, we think it may be better to present admins with a choice of...
In the KVS module a checkpoint is done right before the module exits. However `content.flush` is not called. Thus there is a chance the checkpoint is invalid b/c it is...
Per discussion in #6169 Support a new "preallocate" config & module option to pre-allocate a specific amount of space to sqlite so that we can hopefully avoid ENOSPC issues when...