[GitHub] [iotdb] neuyilan opened a new pull request #3029: [IOTDB-1317]fix the bug that Log CatchUp always failed du to not check the follow…

[GitBox <gi...@apache.org>]

neuyilan opened a new pull request #3029:
URL: https://github.com/apache/iotdb/pull/3029


   https://issues.apache.org/jira/browse/IOTDB-1317
   
   When the follower lags behind the leader, it will catch up with the leader through the log. When it can't find the logs to catch up with in the memory of the leader, it will go to the file on the local disk to find the satisfied logs. The logs found are between the old match index and the commit index saved by the leader. However, at this time, the match index of the follower may have been updated and the old match index of the follower may have been deleted (in order to prevent a large number of logs from being kept on disk, there is a log deletion mechanism). So at this time, if you send the above logs to the follower, the follower will fail to find the matching log. At this time, this storage group will appear to write stuck phenomenon.
   
   The solution is to re-check the match index of the follower after reading the log from the disk.
   
   


-- 
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.

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

[GitHub] [iotdb] mychaow merged pull request #3029: [IOTDB-1317] Log CatchUp always failed du to not check the follower's match index

[GitBox <gi...@apache.org>]

mychaow merged pull request #3029:
URL: https://github.com/apache/iotdb/pull/3029


   


-- 
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.

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