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
I wonder if it would be easier to implement a limit on storing a large value in the first place?
I hate to suggest modifying RFC 11 but we could maybe consider adding an optional size to val and valref?
(optional in the sense that it is allowed to be missing from older metadata)
If we have a running total size for a kvs value, then we have the means to reject an append that would cause it to exceed some maximum.
The text was updated successfully, but these errors were encountered:
Per discussion in #6256
The text was updated successfully, but these errors were encountered: