mirror of
https://github.com/status-im/consul.git
synced 2025-01-11 14:24:39 +00:00
Doc changes in response to review.
This commit is contained in:
parent
598526eba2
commit
1f330add02
@ -74,10 +74,10 @@ from `1`.
|
|||||||
|
|
||||||
Note: there is more information about [checks here](/docs/agent/checks.html).
|
Note: there is more information about [checks here](/docs/agent/checks.html).
|
||||||
|
|
||||||
The `enableTagOverride` can optionally specified to disable the antientropy feature for
|
The `enableTagOverride` can optionally be specified to disable the anti-entropy
|
||||||
this service. If `enableTagOverride` is set to TRUE then external agents can
|
feature for this service. If enableTagOverride is set to TRUE then external
|
||||||
reregister this service and modify the tags. Subsequent local sync operations
|
agents can update this service in the [catalog](/docs/agent/http/catalog.html) and modify the tags. Subsequent
|
||||||
by this agent will ignore the updated tags. For instance: If an external agent
|
local sync operations by this agent will ignore the updated tags. For instance: If an external agent
|
||||||
modified both the tags and the port for this service and `enableTagOverride`
|
modified both the tags and the port for this service and `enableTagOverride`
|
||||||
was set to TRUE then after the next sync cycle the service's port would revert
|
was set to TRUE then after the next sync cycle the service's port would revert
|
||||||
to the original value but the tags would maintain the updated value. As a
|
to the original value but the tags would maintain the updated value. As a
|
||||||
|
@ -138,8 +138,8 @@ automatically recover from these types of transient failures.
|
|||||||
|
|
||||||
### EnableTagOverride
|
### EnableTagOverride
|
||||||
|
|
||||||
Synchronization of service registration can be partially modified to allow
|
Synchronization of service registration can be partially modified to allow
|
||||||
external agents change the tag value of a service. This can be useful in
|
external agents to change the tags for a service. This can be useful in
|
||||||
situations where an external monitoring service needs to be the source of
|
situations where an external monitoring service needs to be the source of
|
||||||
truth for tag information. For instance: Redis DB and its monitoring service
|
truth for tag information. For instance: Redis DB and its monitoring service
|
||||||
Redis Sentinel have this kind of relationship. Redis instances are responsible
|
Redis Sentinel have this kind of relationship. Redis instances are responsible
|
||||||
|
Loading…
x
Reference in New Issue
Block a user