[
https://issues.apache.org/jira/browse/RATIS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh resolved RATIS-537.
-------------------------------------
Resolution: Implemented
This is already implemented with RATIS-352. Sorry for the confusion.
{code}
private void logMetadata(long commitIndex) {
raftLog.appendMetadata(currentTerm, commitIndex);
notifySenders();
}
{code}
> Commit indexes on followers should be updated soon after leader commits an
> index
> --------------------------------------------------------------------------------
>
> Key: RATIS-537
> URL: https://issues.apache.org/jira/browse/RATIS-537
> Project: Ratis
> Issue Type: Bug
> Components: server
> Affects Versions: 0.3.0
> Reporter: Mukul Kumar Singh
> Priority: Major
>
> For Ozone, the client watches for the commit indexes to catch up.
> However after the leader commits an index in its log, it takes the next
> heartbeat to update the index on the follower.
> This introduces an unnecessary delay in the protocol as watch for commit
> catch up takes time.
> This can be optimized by forcing a heartbeat soon after the commit index is
> updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
