[FIXED] Avoid filestore corruption by rejecting large publishes into JetStream #6798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have an effective and seemingly undocumented limit of 32MB for messages published into JetStream as
indexCacheBuf
in the filestore rejects any records that exceed this length. We did not catch this on publish however, and thenindexCacheBuf
would later error when consuming etc.Related: #6797
Signed-off-by: Neil Twigg [email protected]