[ARVADOS] updated: 2.1.0-913-g41fd5332b

[Git user]

Summary of changes:
 doc/architecture/dispatchcloud.html.textile.liquid | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

       via  41fd5332b48e4256fed1a9d22141ca6ad9b482b4 (commit)
      from  f256d787c2f907208736c118de52cae94a2a74fb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 41fd5332b48e4256fed1a9d22141ca6ad9b482b4
Author: Tom Clegg <tom at curii.com>
Date:   Wed Jun 9 09:06:45 2021 -0400

    17705: Mention IdleBehavior tag name.
    
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at curii.com>

diff --git a/doc/architecture/dispatchcloud.html.textile.liquid b/doc/architecture/dispatchcloud.html.textile.liquid
index cc7cb24f6..c0a5c26e2 100644
--- a/doc/architecture/dispatchcloud.html.textile.liquid
+++ b/doc/architecture/dispatchcloud.html.textile.liquid
@@ -74,7 +74,7 @@ h2. Automatic instance shutdown
 
 Normally, the dispatcher shuts down any instance that has remained idle for 1 minute (see TimeoutIdle configuration) but there are some exceptions to this rule. If the cloud provider returns a quota error when trying to create a new instance, the dispatcher shuts down idle nodes right away, in case the idle nodes are contributing to the quota. Also, the operator can use the management API to set an instance’s idle behavior to “drain” or “hold”. “Drain” shuts down the instance as soon as it becomes idle, which can be used to recycle a suspect node without interrupting a running container. “Hold” keeps the instance alive indefinitely without scheduling additional containers on it, which can be used to investigate problems like a failed startup script.
 
-Each instance is tagged with its current idle behavior, which makes it visible in the cloud provider’s console and ensures the behavior is retained if dispatcher restarts.
+Each instance is tagged with its current idle behavior (using the tag name “IdleBehavior”), which makes it visible in the cloud provider’s console and ensures the behavior is retained if dispatcher restarts.
 
 h2. Management API
 

-----------------------------------------------------------------------


hooks/post-receive
--