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.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 08 Dec, 2018 3 commits
-
-
Mahmood Ali authored
-
Mahmood Ali authored
executor: kill all container processes
-
Nick Ethier authored
Recover from any possible io error when invoking Write on FileRotator
-
- 07 Dec, 2018 4 commits
-
-
Alex Dadgar authored
Don't GC running but desired stop allocations
-
Marcin Matlaszek authored
As of now, FileRotator uses bufio.Write under the hood to write data to configured output file. Due to the way how bufio handles any occurred io error - saves it into `err` variable never resetting it automatically - any operation like `Write`, `Flush` etc will become a no-op, returning the very same, saved error (eg. Out of disk space) even when the problem is fixed (eg. disk space is available again). That automatically means that FileRotator will stop writing any logs, reporting the same error over and over again, even if it's no longer valid. This PR fixes it by resetting the bufio Writer, which resets any errors and tries to write requested data.
-
Mahmood Ali authored
Mount Devices in container based drivers
-
Mahmood Ali authored
-
- 06 Dec, 2018 13 commits
-
-
Danielle Tomlinson authored
Re-enable Client GC tests
-
Mahmood Ali authored
Fix docker driver tests
-
Danielle Tomlinson authored
-
Mahmood Ali authored
deviceDir is used for specifying mount/device host paths, and those should be absolute paths.
-
Mahmood Ali authored
-
Mahmood Ali authored
Also, LXC requires target paths to be relative. Container paths in LXC binds should never be absolute paths, so we strip any preceeding `/`, even if a user sets one.
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Michael Lange authored
UI: Keep line charts in their canvases at all times
-
Danielle Tomlinson authored
The previous integration test was broken during the client refactor, and it seems to be some sort of race with state updating. I'm going to try and construct a replacement test as part of work on performance, but for now, the underlying behaviour is still being tested.
-
Danielle Tomlinson authored
-
Danielle Tomlinson authored
-
Michael Lange authored
-
- 05 Dec, 2018 9 commits
-
-
Alex Dadgar authored
Fix various bugs with task events
-
Alex Dadgar authored
Fixes the following: * Emitting events when the task fails to start * Don't double emit events on task shutdown (nomad stop) * Don't emit a OOM kill metric unless actually OOM'd
-
Alex Dadgar authored
This PR fixes an edge case where we could GC an allocation that was in a desired stop state but had not terminated yet. This can be hit if the client hasn't shutdown the allocation yet or if the allocation is still shutting down (long kill_timeout). Fixes https://github.com/hashicorp/nomad/issues/4940
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
Simplify the tests to do all assertions within the main goroutine and account for status propagation delay.
-
Mahmood Ali authored
server/vault: Lock Vault expiration tracking
-
Mahmood Ali authored
tests: fix rkt tests
-
Mahmood Ali authored
0.8.6 uses exit code 1 when `proc.Wait()` fails: https://github.com/hashicorp/nomad/blob/v0.8.6/client/driver/executor/executor.go#L442
-
- 04 Dec, 2018 11 commits
-
-
Mahmood Ali authored
The rkt command itself needs an environment with PATH set to find iptables.
-
Preetha authored
Add guards around subtracting summary count
-
Mahmood Ali authored
Also update the new recommended `nomad job` subcommands
-
Dan Brown authored
* Add Nomad RA * Add deployment guide and nav * Deployment Guide update * Minor typo fixes * Update diagrams * Fixes for review * Link fixes and typo fix * Edits following review - Update image text from "zone" to "datacenter" to match Nomad terminology - Clean up text based on Preetha's feedback * Text updates Based on feedback from Rob * Update diagrams * fixing spelling * Add suggestions from Preetha and Omar
-
Mahmood Ali authored
-
Mahmood Ali authored
WaitForResult expects body to fail and retries few times before giving up. Assertions inside the testfn body causes it to terminate abruptly without retrying.
-
Mahmood Ali authored
`currentExpiration` field is accessed in multiple goroutines: Stats and renewal, so needs locking. I don't anticipate high contention, so simple mutex suffices.
-
Mahmood Ali authored
When `t.Parallel()` is used inside a `t.Run()` sub-set, the closure doesn't behave as expected, and some cases effectively get skipped. More details can be found in https://gist.github.com/posener/92a55c4cd441fc5e5e85f27bca008721
-
Mahmood Ali authored
-
Mahmood Ali authored
Some tests have containers that die almost immediately, and may die and cleaned up before `driver.WaitUntilStarted` runs. The causes for container dying seems special for each test: * TestDockerDriver_Cleanup: `hello-world` image just emits a message and exits immediately * TestDockerDriver_ForcePull_RepoDigest: the busybox image in `TestDockerDriver_ForcePull_RepoDigest` test didn't support `-p 0` argument * TestDockerDriver_Entrypoint: with the entrypoint being `/bin/sh -c`, the command needs to be the entire string; otherwise, it ignores the comments
-
Mahmood Ali authored
Currently, libcontainer-based executor, upon shutdown, kills the container initial process. The children of the killed process remain running, and the executor is never marked as terminated until they do. Also, fix a case where we treat processes as successful, when `proc.Wait()` fails. In some attempts, I was getting "waitid no child processes" errors and such error shouldn't get process to be considered successful.
-