Deepak-Vohra

With both constraints added the result is not consistent. Earlier all but 2 of the 10 replicas stopped running within 5 minutes. When tested again, all but two replicas are...

Still, all but two replicas are running even after more than 20 minutes. How could replicas be running with the placement constraints not being applied? ``` Constraints": [ "node.role==worker", "node.role==manager"...

``` core@ip-10-0-0-238 ~ $ docker version Client: Version: 1.12.6 API version: 1.24 Go version: go1.6.3 Git commit: d5236f0 Built: Tue Jan 31 07:56:17 2017 OS/Arch: linux/amd64 Server: Version: 1.12.6 API...

As role cannot be both manager and worker replicas should not be running with both roles applied as constraints.

With Parallelism as 1 two replicas would be made non running. But in an earlier run all but two (8 out of 10) replicas were made non running.

Shouldn't update be the same. At least have some consistency.

_If you put these constraints on service create, no instance would advance to running._ Got the result indicated. But stays Allocated. No provision to set timeout.

The issue is different, about service constraints, which are node role based.

_better to fail this update with timeout mechanism_ Is a timeout provided for `service create` and `service update`? Did not find any.

Yes, thanks. update should probably include a timeout and a rollback option.