This project is mirrored from https://gitee.com/mirrors/nomad.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 25 Aug, 2019 1 commit
    • Mahmood Ali's avatar
      Don't persist allocs of destroyed alloc runners · a80643e4
      Mahmood Ali authored
      This fixes a bug where allocs that have been GCed get re-run again after client
      is restarted.  A heavily-used client may launch thousands of allocs on startup
      and get killed.
      
      The bug is that an alloc runner that gets destroyed due to GC remains in
      client alloc runner set.  Periodically, they get persisted until alloc is
      gced by server.  During that  time, the client db will contain the alloc
      but not its individual tasks status nor completed state.  On client restart,
      client assumes that alloc is pending state and re-runs it.
      
      Here, we fix it by ensuring that destroyed alloc runners don't persist any alloc
      to the state DB.
      
      This is a short-term fix, as we should consider revamping client state
      management.  Storing alloc and task information in non-transaction non-atomic
      concurrently while alloc runner is running and potentially changing state is a
      recipe for bugs.
      
      Fixes https://github.com/hashicorp/nomad/issues/5984
      Related to https://github.com/hashicorp/nomad/pull/5890
      a80643e4
  2. 24 Aug, 2019 2 commits
  3. 23 Aug, 2019 13 commits
  4. 22 Aug, 2019 9 commits
  5. 21 Aug, 2019 8 commits
  6. 20 Aug, 2019 7 commits