[server] Valid value of LOG_SEGMENT_FILE_SIZE #1504
Merged
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.
Purpose
Currently, the value of
log.segment.file-sizeis configured byMemorySizewhich could be vary large. But in fluss sever we use Javaintto representlog.segment.file-size. Actually the max value oflog.segment.file-sizeis 2GB -1 (Integer.MAX_VALUEbytes). I think we need to valid this value and fail fast if it has been set too large.Brief change log
Tests
API and Format
Documentation