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. 19 Apr, 2022 8 commits
  2. 14 Apr, 2022 1 commit
  3. 12 Apr, 2022 1 commit
  4. 11 Apr, 2022 2 commits
  5. 08 Apr, 2022 4 commits
  6. 31 Mar, 2022 3 commits
  7. 30 Mar, 2022 1 commit
  8. 14 Mar, 2022 3 commits
  9. 10 Mar, 2022 2 commits
  10. 08 Mar, 2022 2 commits
  11. 01 Mar, 2022 6 commits
  12. 10 Feb, 2022 7 commits
    • Nomad Release Bot's avatar
      Release v1.2.6 · 95514d56
      Nomad Release Bot authored
      95514d56
    • Nomad Release bot's avatar
      Generate files for 1.2.6 release · a6c6b475
      Nomad Release bot authored
      a6c6b475
    • Luiz Aoqui's avatar
      docs: add 1.2.6 to changelog · a3319d7d
      Luiz Aoqui authored
      a3319d7d
    • Tim Gross's avatar
      scheduler: prevent panic in spread iterator during alloc stop · c49359ad
      Tim Gross authored
      The spread iterator can panic when processing an evaluation, resulting
      in an unrecoverable state in the cluster. Whenever a panicked server
      restarts and quorum is restored, the next server to dequeue the
      evaluation will panic.
      
      To trigger this state:
      * The job must have `max_parallel = 0` and a `canary >= 1`.
      * The job must not have a `spread` block.
      * The job must have a previous version.
      * The previous version must have a `spread` block and at least one
        failed allocation.
      
      In this scenario, the desired changes include `(place 1+) (stop
      1+), (ignore n) (canary 1)`. Before the scheduler can place the canary
      allocation, it tries to find out which allocations can be
      stopped. This passes back through the stack so that we can determine
      previous-node penalties, etc. We call `SetJob` on the stack with the
      previous version of the job, which will include assessing the `spread`
      block (even though the results are unused). The task group spread info
      sta...
      c49359ad
    • Luiz Aoqui's avatar
      api: prevent excessice CPU load on job parse · 1aa3b561
      Luiz Aoqui authored
      Add new namespace ACL requirement for the /v1/jobs/parse endpoint and
      return early if HCLv2 parsing fails.
      
      The endpoint now requires the new `parse-job` ACL capability or
      `submit-job`.
      1aa3b561
    • Seth Hoenig's avatar
      client: check escaping of alloc dir using symlinks · b3c0e6a7
      Seth Hoenig authored
      This PR adds symlink resolution when doing validation of paths
      to ensure they do not escape client allocation directories.
      b3c0e6a7
    • Seth Hoenig's avatar
      client: fix race condition in use of go-getter · 6445da9b
      Seth Hoenig authored
      go-getter creates a circular dependency between a Client and Getter,
      which means each is inherently thread-unsafe if you try to re-use
      on or the other.
      
      This PR fixes Nomad to no longer make use of the default Getter objects
      provided by the go-getter package. Nomad must create a new Client object
      on every artifact download, as the Client object controls the Src and Dst
      among other things. When Caling Client.Get, the Getter modifies its own
      Client reference, creating the circular reference and race condition.
      
      We can still achieve most of the desired connection caching behavior by
      re-using a shared HTTP client with transport pooling enabled.
      6445da9b