From 8bbc2c3f33d37e7f3ce9a324dcf0e209369a59df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Fri, 10 Aug 2018 10:00:53 +0300 Subject: [PATCH] MXS-1929: Clarify service destruction The prgress of service destruction can be monitored via the `sessions` endpoint. --- Documentation/REST-API/Resources-Service.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/REST-API/Resources-Service.md b/Documentation/REST-API/Resources-Service.md index f8baceefd..38f22e8f3 100644 --- a/Documentation/REST-API/Resources-Service.md +++ b/Documentation/REST-API/Resources-Service.md @@ -331,6 +331,10 @@ they are allowed to gracefully close before the service is destroyed. This means that the destruction of a service can be acknowledged via the REST API before the destruction process has fully completed. +To find out whether a service is still in use after it has been destroyed, the +[`sessions`](./Resources-Session.md) resource should be used. If a session for +the service is still open, it has not yet been destroyed. + #### Response Service is destroyed: