[Java] Add support for changing term buffer length and MTU in the Cluster log. #1233
<
8000
div class="d-flex flex-order-2 flex-md-order-1 mx-2">
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.
This PR adds a feature that allows a Cluster to be restarted with the term buffer length and/or MTU changed. This requires truncating an existing recording log to the latest valid snapshot, i.e. Cluster is starting from a snapshot only. The new API to do such truncation is provided via the
ClusterTool
(i.e.io.aeron.cluster.ClusterTool#truncateRecordingLog
andtruncate-recording-log
command).Besides this feature this PR also contains a fix for keeping entries properly sorted in the
RecodingLog
.