1. 12 Sep, 2022 1 commit
    • Ozan Tezcan's avatar
      Handle response error cases gracefully (#137) · 8db9930c
      Ozan Tezcan authored
      A node can receive responses from followers who are not
      aware of they have been removed from the cluster configuration.
      In this case, recv_ family functions can be called without 
      a node structure. We should ignore these messages.
      
      We should also ignore snapshot and appendentries responses
      if we are not leader anymore. Returning an error code for 
      this case does not make sense because application cannot 
      do anything but ignore the error code. 
      
      This PR changes return value to zero for these cases. 
      8db9930c
  2. 05 Sep, 2022 1 commit
  3. 04 Sep, 2022 1 commit
  4. 30 Aug, 2022 1 commit
    • Ozan Tezcan's avatar
      Refactor debug logging (#127) · e79d3b6a
      Ozan Tezcan authored
      Refactor debug logging and change log callback
      
      e.g:
      19 --> 13, sent snapshot_resp id:27712, t:24, s:1, o:4096, lc:0
      14 --> 17, sent requestvote_req pv:1, t:25, ci:14, lli:6848, llt:23
      14 <-- 17, recv requestvote_resp pv:1, t:25, rt:24, vg:0
      
      Breaking changes: 
      
      raft_log_f() callback will not pass node_id_t anymore.
      Sender and receiver will be part of the log line as you can see above.
      e79d3b6a
  5. 29 Aug, 2022 1 commit
    • Ozan Tezcan's avatar
      Simplify entry removal (#130) · c0270e61
      Ozan Tezcan authored
      Simplied pop callback.
      
      Previously, libraft was passing a callback(raft_entry_notify_f) to the pop callback.
      The application was supposed to call that callback for each removed entry.
      
      Libraft can loop over the entries and call the required functions itself.
      So, we can delete raft_entry_notify_f from the pop callback just to
      simplify API.
      
      In addition to that, this PR removes raft_pop_entry() function which doesn't have
      a use-case, as far as I can see.
      We can use raft_delete_entry_from_idx(me, raft_get_current_idx()) instead if required.
      c0270e61
  6. 28 Aug, 2022 1 commit
  7. 25 Aug, 2022 2 commits
    • Ozan Tezcan's avatar
      Fix memory leak in raft_restore_log() (#126) · f1ab5203
      Ozan Tezcan authored
      f1ab5203
    • Ozan Tezcan's avatar
      Add support to rebuild configuration after a restart (#125) · 9c09a6cc
      Ozan Tezcan authored
      Configuration changes are special in Raft. They take effect 
      whenever the related log entries are appended. On a restart, 
      we should go over the log entries and rebuild the configuration.
      
      Adding raft_restore_log() function for this purpose.
      
      Overall, on a restart, application should do:
      
      Load the snapshot and call raft_restore_snapshot()
      Load the log entries and call raft_restore_log()
      Read the metadata file and call raft_restore_metadata().
      9c09a6cc
  8. 23 Aug, 2022 2 commits
  9. 22 Aug, 2022 1 commit
    • Ozan Tezcan's avatar
      Improve snapshot support (#121) · 7d66a156
      Ozan Tezcan authored
      - raft_load_snapshot_f(): Changed order of arguments term and index
      to be inline with raft_begin_load_snapshot().
      
      - Refactored raft_begin_load_snapshot(). Now, inside this function, 
      current server's node flags are cleared. Previously, application had to
      take care of it. e.g Application had to clear inactive flag on a snapshot.
      
      - Added raft_restore_snapshot() to let libraft know that application has
      loaded a snapshot.
      7d66a156
  10. 16 Aug, 2022 2 commits
  11. 08 Aug, 2022 1 commit
  12. 07 Jul, 2022 1 commit
    • Ozan Tezcan's avatar
      Throttle operations early not to block server (#108) · 40100cfa
      Ozan Tezcan authored
      Throttle operations early not to block server
      
      Introduced throttling in #106. If execution of operations take as much as request-timeout, it means this server will not generate responses on time for the existing requests. This is causing extra elections. I've changed deadline as 'now + request_timeout / 2', giving server some room for other operations and enough time to send responses.
      40100cfa
  13. 05 Jul, 2022 1 commit
    • Ozan Tezcan's avatar
      Do not execute operations in periodic when auto_flush is off (#109) · 03e2f294
      Ozan Tezcan authored
      Do not execute operations in periodic when auto_flush is off 
      
      Introduced auto_flush config in #81. If auto_flush is off, application is supposed to call raft_flush() manually. This function increments commit index, applies entries and sends appendentries requests.
      
      Currently, we execute operations in raft_periodic() and raft_flush() both. When auto_flush is off, it makes sense to leave execution to raft_flush() to do it in a single place.
      03e2f294
  14. 30 Jun, 2022 1 commit
  15. 19 Jun, 2022 1 commit
  16. 19 May, 2022 1 commit
  17. 15 May, 2022 1 commit
  18. 02 May, 2022 1 commit
  19. 26 Apr, 2022 1 commit
  20. 25 Apr, 2022 1 commit
  21. 18 Apr, 2022 1 commit
  22. 04 Apr, 2022 1 commit
  23. 03 Apr, 2022 1 commit
  24. 30 Mar, 2022 2 commits
  25. 24 Mar, 2022 1 commit
  26. 21 Mar, 2022 1 commit
  27. 13 Mar, 2022 4 commits
  28. 08 Mar, 2022 1 commit
  29. 06 Mar, 2022 1 commit
  30. 07 Feb, 2022 1 commit
  31. 07 Dec, 2021 1 commit
  32. 15 Nov, 2021 1 commit
  33. 03 Nov, 2021 1 commit
    • Shaya Potter's avatar
      set next_idx on each succesful raft_send_appendentries call (#65) · 02bdf818
      Shaya Potter authored
      this is to avoid sending duplicate entries each time raft_send_appendentries is called, just because they haven't been acked yet.
      
      it will still be reset backwards upon the leader receiving a raft_recv_appendentries_response() with a failure mode
      
      + a test for next_idx on append entry, which changes a number of tests which checked for this
      
      in order to do this, I had to modify the existing mock callback to return 0 instead of 1.  this needs to be verified
      
      + fixes for raft tests that this change exposed
      
      1) when we issues a sequence of entries, each was given an increasing term, so had entries whose term was higher than leaders term
      
      so had to fix that
      
      2) by setting the term of appendentries_repsonse to not be equal to leaders term (because of fix above), we now fail on receiving them
      
      do all that by not allowing raft_append_entry to append an entry that break raft semantics (i.e. term of entry > log term), but this breaks many tests that don't set term, so set them
      02bdf818