KöpBuy
1-855-856-7678
SupportSupport
EN
Det här innehållet finns inte tillgängligt på ditt språk men här finns den engelska versionen,
Reboot Role Instance
Updated: October 11, 2011
The Reboot Role Instance operation requests a reboot of a role instance that is running in a deployment.
The Reboot Role Instance operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests.
Request
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, <deployment-name> with the name of your deployment, and <role-instance-name> with the name of your role instance.
| Method | Request URI | HTTP Version |
|---|---|---|
|
POST |
|
HTTP/1.1 |
|
POST |
|
HTTP/1.1 |
URI Parameters
| URI Parameter | Description |
|---|---|
|
comp=reboot |
Required. Specifies that the instance of the role must be rebooted. |
Request Headers
The following table describes the request headers.
| Request Header | Description |
|---|---|
|
Content-Type |
Required. Set this header to |
|
x-ms-version |
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 later. For more information about versioning headers, see Service Management Versioning. |
|
ContentLength |
Required. Must be set to 0. |
Request Body
None.
Response
The response includes an HTTP status code and a set of response headers.
Because Reboot Role Instance is an asynchronous operation, you must call Get Operation Status to determine whether the operation is complete, has failed, or is still in progress.
Status Code
Because Reboot Role Instance is an asynchronous operation, it always returns status code 202 (Accept). To determine the status code for the operation once it is complete, call Get Operation Status. The status code is embedded in the response for this operation; if successful, it will be status code 200 (OK). For information about status codes, see Service Management Status and Error Codes.
Response Headers
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.
| Response Header | Description |
|---|---|
|
x-ms-request-id |
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. See Tracking Asynchronous Service Management Requests for more information. |
Response Body
None.
Authorization
Any management certificate associated with the subscription specified by <subscription-id> can be used to authenticate this operation. For additional details, see Authenticating Service Management Requests.
Remarks
When you reboot a role instance, Windows Azure takes the instance offline, restarts the underlying operating system for that instance, and brings the instance back online. Any data that is written to the local disk is persisted across reboots. Any data that is in-memory is lost.
