3e96c6c4e0
Address more code review feedback
2018-03-14 16:10:32 -05:00
9fed0d2103
Get reschedule policy from the alloc directly
2018-03-14 16:10:32 -05:00
e89bbf7289
Update comment about WaitTime
2018-03-14 16:10:32 -05:00
47e0280d96
More small review feedback
2018-03-14 16:10:32 -05:00
5373ade731
Scheduler and Reconciler changes to support delayed rescheduling
2018-03-14 16:10:32 -05:00
2ed4de7e7b
Track previous node id correctly, plus unit test
2018-01-31 09:58:05 -06:00
ea4a889e28
Address more code review feedback
2018-01-31 09:56:53 -06:00
bd89d2b39e
Make sure that reschedule trackers are not added for node drain replacements
2018-01-31 09:56:53 -06:00
21b7b79d5d
Add helper methods, use require and other code review feedback
2018-01-31 09:56:53 -06:00
d0f9d59abb
Reconile with changes to structs for reschedule tracking
2018-01-31 09:56:53 -06:00
fbb1936dee
Fix some comments and lint warnings, remove unused method
2018-01-31 09:56:53 -06:00
031c566ada
Reschedule previous allocs and track their reschedule attempts
2018-01-31 09:56:53 -06:00
3b4d7ac2a3
Fix some typos
2017-12-14 13:29:27 -06:00
c1cc51dbee
sync
2017-10-13 14:36:02 -07:00
a66c53d45a
Remove `structs` import from `api`
...
Goes a step further and removes structs import from api's tests as well
by moving GenerateUUID to its own package.
2017-09-29 10:36:08 -07:00
3904bde9a3
Fix batch handling of complete allocs/node drains
...
This PR fixes:
* An issue in which a node-drain that contains a complete batch alloc
would cause a replacement
* An issue in which allocations with the same name during a scale
down/stop event wouldn't be properly stopped.
* An issue in which batch allocations from previous job versions may not
have been stopped properly.
Fixes https://github.com/hashicorp/nomad/issues/3210
2017-09-14 15:08:57 -07:00
84d06f6abe
Sync namespace changes
2017-09-07 17:04:21 -07:00
184bfd4836
Better comment
2017-07-20 12:31:08 -07:00
248315a2d9
Handle destructive changes before placements
...
This PR updates the generic scheduler to handle destructive changes
before handling placements. This is important because the destructive
change may be due to a lowering of resources. If this is the case, the
handling of the destructive changes first may make it possible for the
placement to happen.
To reason about this imagine there is one node with CPU = 500.
If the group originally had:
* `count = 1`
* `cpu = 400`
And then the job was updated such that the group had:
* `count = 4`
* `cpu = 120`
If the original alloc isn't discounted first, nothing would be able to
place.
2017-07-20 12:24:27 -07:00
641e178416
Stop before trying to place
2017-07-17 17:18:12 -07:00
66a90326e1
Treat destructive updates atomically
2017-07-16 10:35:38 -07:00
f86760db3c
Basic logs
2017-07-07 16:49:08 -07:00
20005f925a
Rolling node drains using max_parallel and stagger
...
This PR adds rolling node drains done at max_parallel and stagger of the
update spec. It brings it inline with old behavior.
2017-07-07 12:12:48 -07:00
d352d85bb9
Test scheduler's handling of canaries/inplace updates
2017-07-07 12:10:04 -07:00
e229d3650b
Attach eval id
2017-07-07 12:10:04 -07:00
af1935e1e1
Mark complete
2017-07-07 12:10:04 -07:00
8424a3b380
Change canary handling
2017-07-07 12:10:04 -07:00
09dfa2fc10
Rename CreateDeployments and remove cancelling behavior in state_store
2017-07-07 12:10:04 -07:00
067ed86a47
Client watches for allocation health using task state and Consul checks
...
This PR adds watching of allocation health at the client. The client can
watch for health based on the tasks running on time and also based on
the consul checks passing.
2017-07-07 12:10:04 -07:00
27a6e6b6d1
update description of the alloc update factory function
2017-07-07 12:03:11 -07:00
b2573b01f9
Fix canary handling
2017-07-07 12:03:11 -07:00
d111dd5c10
Pull out in-place updating into a passed in function; reduce inputs to reconciler
2017-07-07 12:03:11 -07:00
4c123500ee
Remove old
2017-07-07 12:03:11 -07:00
cf5baba808
handle annotations
2017-07-07 12:03:11 -07:00
07b1c3e5db
Only upsert a job if the spec changes and push deployment creation into reconciler
2017-07-07 12:03:11 -07:00
0d42b5d421
initial reconciler
2017-07-07 12:01:17 -07:00
b3f4db0930
cancel deployments
2017-07-07 12:01:17 -07:00
5a2449d236
Respond to review comments
2017-04-19 10:54:03 -07:00
3145086a42
non-purge deregisters
2017-04-15 17:08:05 -07:00
b69b357c7f
Nomad builds
2017-02-07 20:31:23 -08:00
5191b4d33a
Making the status command return the allocs of currently registered job
2016-11-24 16:31:30 +01:00
dae7f88118
Not setting a drained node as preferred node ( #1740 )
2016-09-23 21:15:50 -07:00
1b3c5e98c8
Renaming LocalDisk to EphemeralDisk ( #1710 )
...
Renaming LocalDisk to EphemeralDisk
2016-09-14 15:43:42 -07:00
52e9946da9
Implemented SetPrefferingNodes in stack
2016-08-30 16:17:50 -07:00
bfee7b30a3
Introducing shared resources in alloc
2016-08-29 13:49:25 -07:00
13497913f9
Ensuring resources are re-calculated properly in fsm
2016-08-26 20:13:11 -07:00
3447658bba
Added scheduler tests to ensure disk constraints are honored
2016-08-25 15:31:56 -05:00
1de89776d7
Marking an allocation chained if we are creating this to replace an old one
2016-08-15 17:52:41 -07:00
13bab5b1ad
Added scheduler tests
2016-08-09 14:52:25 -07:00
ab94c8eed9
Marking allocations which are not terminal and are on down nodes as lost
2016-08-09 13:11:58 -07:00
Preetha Appan