[
https://issues.apache.org/jira/browse/RATIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584542#comment-16584542
]
Rajeshbabu Chintaguntla edited comment on RATIS-253 at 8/18/18 12:48 AM:
-------------------------------------------------------------------------
[~msingh][~szetszwo] Here is the patch not including the statemachine data size
while calculating entry size. Please review.
was (Author: rajeshbabu):
[~msingh][~szetszwo] Here is the patch not including the statemachine data size
while calculating entry size.
> Segmented Raft log rolls over segment frequently
> ------------------------------------------------
>
> Key: RATIS-253
> URL: https://issues.apache.org/jira/browse/RATIS-253
> Project: Ratis
> Issue Type: Bug
> Components: server
> Affects Versions: 0.2.0
> Reporter: Mukul Kumar Singh
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Labels: ozone
> Attachments: RATIS-253.patch
>
>
> With statemachine implementation which abstract out the state machine data
> from the append entries, frequent log rollovers can be observed.
> Looking into the code, this seems to be because of 2 reasons.
> a) LogSegment#append, updates the total size. However the size which needs to
> be considered should not include the statemachine data.
> b) Also SegmentRaftLog#isSegmentFull also considers the total proto object.
> Here too, only the entry to be written to the log should be considered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
