[PR] RATIS-2717. Fix incorrect size accounting in SegmentedRaftLogReader.decodeEntry() [ratis]

["lugency (via GitHub)" <gi...@apache.org>]

lugency opened a new pull request, #1611:
URL: https://github.com/apache/ratis/pull/1611

   ## What changes were proposed in this pull request?
   
   `SegmentedRaftLogReader` can reject an entry whose serialized size is within `maxOpSize`, because the on-disk record also contains a varint length prefix and a four-byte checksum.
   
   - This change accounts for the length prefix in the temporary-buffer bound and for both the prefix and checksum in the read limit and mark range, while retaining the serialized-entry size check.
   
   - It also adds `testReadEntryAtMaxOpSize` to verify that an entry can be read when its serialized size equals `maxOpSize`, and closes resources in two existing read/write tests.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/RATIS-2717
   
   ## How was this patch tested?
   
   Tested locally:
   - `TestRaftLogReadWrite`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ratis.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] RATIS-2717. Fix incorrect size accounting in SegmentedRaftLogReader.decodeEntry() [ratis]

["szetszwo (via GitHub)" <gi...@apache.org>]

szetszwo merged PR #1611:
URL: https://github.com/apache/ratis/pull/1611


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ratis.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org