[ https://issues.apache.org/jira/browse/RATIS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee updated RATIS-801: -------------------------------------- Description: Currently, while triggering snapshot, snapshotUpdater#appliedIndex is taken into account to decide whether it has exceeded the snapshot threshold from the last snapshotIndex. This may lead to creating more snapshots than usual as stateMachineUpdater#appliedIndex is updated as soon as the applyTransaction call happens. Ideally, Ratis snapshot should not be triggered taking stateMachine's applied index into account. (was: Currently, while triggering snapshot, snapshotUpdater#appliedIndex is taken into account to decide whether it has exceeded the snapshot threshold from the last snapshotIndex. This may lead to creating more snapshots than usual as stateMachineUpdater#appliedIndex is updated as soon as the applyTransaction call happens. Ideally, Ratis snapshot should nbe triggered taking stateMachine's applied index into account.) > Ratis snapshot should consider stateMachine#appliedIndex for triggering > snapshot > -------------------------------------------------------------------------------- > > Key: RATIS-801 > URL: https://issues.apache.org/jira/browse/RATIS-801 > Project: Ratis > Issue Type: Improvement > Affects Versions: 0.5.0 > Reporter: Shashikant Banerjee > Assignee: Bharat Viswanadham > Priority: Major > Fix For: 0.6.0 > > > Currently, while triggering snapshot, snapshotUpdater#appliedIndex is taken > into account to decide whether it has exceeded the snapshot threshold from > the last snapshotIndex. This may lead to creating more snapshots than usual > as stateMachineUpdater#appliedIndex is updated as soon as the > applyTransaction call happens. Ideally, Ratis snapshot should not be > triggered taking stateMachine's applied index into account. -- This message was sent by Atlassian Jira (v8.3.4#803005)