Commits on Jun 3, 2019

1. nomad: revert use of SnapshotAfter in planApply …

   Revert plan_apply.go changes from #5411
   
   Since non-Command Raft messages do not update the StateStore index,
   SnapshotAfter may unnecessarily block and needlessly fail in idle
   clusters where the last Raft message is a non-Command message.
   
   This is trivially reproducible with the dev agent and a job that has 2
   tasks, 1 of which fails.
   
   The correct logic would be to SnapshotAfter the previous plan's index to
   ensure consistency. New clusters or newly elected leaders will not have
   a previous plan, so the index the leader was elected should be used
   instead.

   

   schmichael committed Jun 3, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for cd3cd0a
   • Browse repository at this point

   Copy the full SHA

   cd3cd0a View commit details

   Browse the repository at this point in the history