hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1929: Clarify service destruction

Browse Source 
The prgress of service destruction can be monitored via the `sessions`
endpoint.
This commit is contained in:
Markus Mäkelä 2018-08-10 10:00:53 +03:00
parent a399c58df3
commit 8bbc2c3f33
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/REST-API/Resources-Service.md
View File

@ -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: