Reboot Role Instance
Updated: June 29, 2015
The Reboot Role Instance asynchronous operation requests a reboot of a role instance that is running in a deployment.
The Reboot Role Instance request may be specified as follows. Replace <subscription-id> with your subscription ID, <cloudservice-name> with the name of the cloud service, <deployment-slot> with staging or production, or <deployment-name> with the name of your deployment. Replace <role-instance-name> with the name of your role instance.
You must make sure that the request that is made to the management service is secure. For additional details, see Authenticating Service Management Requests.
Required. Specifies that the instance of the role must be rebooted.
The following table describes the request headers.
Required. Set this header to application/xml.
Required. Specifies the version of the operation to use for this request. The value of this header must be set to 2010-10-28 or higher. For more information about versioning headers, see Service Management Versioning.
Required. Must be set to 0.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK). For information about status codes, see Service Management Status and Error Codes.
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
A value that uniquely identifies a request made against the management service. For an asynchronous operation, you can call Get Operation Status with the value of the header to determine whether the operation is complete, has failed, or is still in progress.
When you reboot a role instance, the instance is taken offline, the underlying operating system is restarted for that instance, and the instance is brought back online. Any data that is written to the local disk is persisted across reboots. Any data that is in-memory is lost.