Tim Gross 5e3efbd3ec doc: explain ALLOC_INDEX uniqueness guarantees (#6830) ...

The `ALLOC_INDEX` isn't guaranteed to be unique, and this has caused
some user confusion. The servers make a best-effort attempt to make
this value unique from 0 to count-1 but when you have canaries on the
task group, there are reused indexes because you have multiple job
versions running at the same time. If a user needs a unique number for
interpolating a value in your application, they can get this by
combining the job version and the alloc index.

Co-Authored-By: Michael Schurter <mschurter@hashicorp.com>

2019-12-10 10:30:26 -05:00

..

commands

docs: update quota docs to include network limits

2019-11-20 18:44:06 -05:00

configuration

docs: show /etc/passwd in minimal chroot (#6769)

2019-11-25 13:47:18 -05:00

devices

docs: add lots of links to plugin guide

2019-05-07 10:40:22 -07:00

drivers

docs: address more GH-6762 review comments

2019-11-22 13:22:14 -05:00

enterprise

Fix links to namespace and quotas guides

2019-07-19 12:45:28 -05:00

internals

Update consensus.html.md (#6813)

2019-12-06 06:17:30 -08:00

job-specification

Update network.html.md (#6782)

2019-12-06 06:08:56 -08:00

runtime

doc: explain ALLOC_INDEX uniqueness guarantees (#6830)

2019-12-10 10:30:26 -05:00

telemetry

Add job status metrics

2019-07-26 10:12:49 +01:00

vault-integration

docs: vault integration docs should reference new token_explicit_max_ttl field

2019-12-02 14:22:47 -06:00

faq.html.md

Misc. changes and fixes to docs/

2018-08-25 11:35:56 -05:00

index.html.markdown

Update website to remove a lot of copy-paste with Vault + improve images

2015-09-20 16:37:22 -04:00

schedulers.html.md

Added Sparrow link

2019-05-10 10:35:21 -04:00