[jira] [Updated] (RATIS-253) Segmented Raft log rolls over segment frequently
[ https://issues.apache.org/jira/browse/RATIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated RATIS-253: -- Attachment: RATIS-253.patch > 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)
[jira] [Updated] (RATIS-253) Segmented Raft log rolls over segment frequently
[ https://issues.apache.org/jira/browse/RATIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-253: -- Labels: ozone (was: ) > 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 > > 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)
[jira] [Updated] (RATIS-253) Segmented Raft log rolls over segment frequently
[ https://issues.apache.org/jira/browse/RATIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-253: -- Fix Version/s: (was: 0.2.0) Component/s: server > 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: Mukul Kumar Singh >Priority: Major > > 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)
