Restart running cluster
post
/20260430/aiDataPlatforms/{aiDataPlatformId}/workspaces/{workspaceKey}/clusters/{clusterKey}/actions/restart
Restarts a running cluster.
Request
Path Parameters
-
aiDataPlatformId(required): string
The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the AI Data Platform (Data Lake) instance.
-
clusterKey(required): string
Cluster key.
-
workspaceKey(required): string
The key of the Workspace
Header Parameters
-
if-match: string
For optimistic concurrency control. In the PUT or DELETE call for a resource, set the `if-match` parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
-
opc-retry-token: string
Minimum Length:
1Maximum Length:64A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected.
Details for restarting the cluster.
Root Schema : RestartClusterDetails
Type:
objectDetails to restart a cluster.
Response
Supported Media Types
- application/json
202 Response
Request accepted. Cluster is restarted.
Headers
-
aidp-async-operation-key: string
The key of the asynchronous operations associated with an AI Data Platform instance. Use GetAsyncOperation with this key to track the status of the request.
-
etag: string
For optimistic concurrency control. See `if-match`.
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Cluster
Type:
objectDiscriminator:
sourceApiA Cluster is a compute subresource within AI Data Platform Workbench. Compute/Runtime Clusters are Spark execution environments.
Spark clusters are used for Notebook execution and for Spark SQL query execution over JDBC/ODBC.
These clusters seamlessly process the data in the AI Data Platform Workbench. Users can also use JDBC/ODBC endpoints for highly
performant SQL execution for integration with analytics tools such as Oracle Analytic Cloud and Excel.
A DEFAULT cluster is a subresource within AI Data Platform Workbench associated with master catalog and it can not be
attached to a notebook. A USER cluster is a subresource within workspace and can be attached to a notebook.
Show Source
-
activeClusterResources:
object ActiveClusterResources
Active resources of a cluster.
-
createdBy:
string
OCID of the user who created this record.
-
createdByName:
string
Name of the user who created this record.
-
description:
string
Minimum Length:
1Maximum Length:400Cluster description. -
displayName(required):
string
Cluster name.
-
driverConfig:
object DriverConfig
Driver configuration.
-
key(required):
string
Cluster key.
-
nodeType:
string
Minimum Length:
1Maximum Length:255Cluster node type encodes the node shape and associated resources. -
sourceApi:
string
Default Value:
CLUSTER_APIAllowed Values:[ "CLUSTER_API", "DEFAULT_CLUSTER_API", "AGENT_FLOW_COMPUTE" ]User created clusters are associated with a particular workspace. Default cluster is to be used by all catalogs operations that require compute. Default cluster can be thought of as associated with Master catalog. Agent Flow Compute is used to execute Agent Flows. -
state(required):
string
Allowed Values:
[ "ACCEPTED", "CREATING", "ACTIVE", "DELETING", "DELETED", "FAILED", "STOPPING", "STOPPED", "UPDATING", "RESTARTING", "STARTING", "NETWORK_CONFIGURATION_ATTACH_IN_PROGRESS", "NETWORK_CONFIGURATION_ATTACH_SUCCESSFUL", "NETWORK_CONFIGURATION_ATTACH_FAILED", "NETWORK_CONFIGURATION_DETACH_IN_PROGRESS", "NETWORK_CONFIGURATION_DETACH_SUCCESSFUL", "NETWORK_CONFIGURATION_DETACH_FAILED" ]Common lifecycle states for resources in a compute cluster. ACCEPTED - The resource create request has been accepted. CREATING - The resource is being created and might not be usable until the entire metadata is defined. ACTIVE - The resource is valid and available for access. DELETING - The resource is being deleted, and might require a deep clean of any children. DELETED - The resource has been deleted, and isn't available. FAILED - The resource is in a failed state due to validation or other errors. STOPPING - The resource is being stopped. STOPPED - The resource has been stopped. UPDATING - The resource is being updated and might not be usable until all changes are commited. STARTING - The resource is being started. RESTARTING - The resource is being restarted. -
stateDetails:
string
A message that describes the current state of the workspace cluster in more detail. For example, can be used to provide actionable information for a resource in the Failed state.
-
stoppedBy:
string
OCID of the user who stopped the cluster. Value will be 'SYSTEM' if it was auto stopped.
-
stoppedByName:
string
Name of the user who stopped the cluster. Value will be 'SYSTEM' if it was auto stopped.
-
timeCreated(required):
string(date-time)
Date and time the cluster was created.
-
timeUpdated:
string(date-time)
Date and time the cluster was updated.
-
type:
string
Allowed Values:
[ "USER", "AGENT_FLOW_COMPUTE" ]ClusterType -
updatedBy:
string
OCID of the user who updated this record.
-
updatedByName:
string
Name of the user who updated this record.
Nested Schema : ActiveClusterResources
Type:
objectActive resources of a cluster.
Show Source
-
activeCores:
number(double)
Count of active cores.
-
activeExecutorCount:
number(double)
Count of active executors.
-
activeGpuCores:
number(double)
Count of active GPU cores.
-
activeGpuMemoryInGBs:
number(double)
Active GPU memory in GB.
-
activeMemoryInGBs:
number(double)
Active memory in GB.
Nested Schema : DriverConfig
Type:
objectDriver configuration.
Show Source
-
driverNodeType:
string
Minimum Length:
1Maximum Length:255Node type of optional driver node that encodes the driver node shape and associated resources. -
driverShape:
string
Minimum Length:
1Maximum Length:255Shape of compute cluster driver instance. Example - VM.Standard2.x, VM.Standard.E3.Flex -
driverShapeConfig:
object ShapeConfig
Shape of the driver or executor if a flexible shape is used.
Nested Schema : ShapeConfig
Type:
objectShape of the driver or executor if a flexible shape is used.
Show Source
-
gpus:
integer
Minimum Value:
0Total number of GPUs used for the driver or workers. -
memoryInGBs:
integer
Minimum Value:
16Amount of memory used for the driver or workers. -
ocpus:
integer
Minimum Value:
1Total number of OCPUs used for the driver or workers.
400 Response
Bad Request (invalid query parameters, malformed headers, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
401 Response
Unauthorized (missing or expired credentials, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
404 Response
Not Found. The requested resource was not found.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
409 Response
Conflict. Request conflicts with the current state of the resource.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
412 Response
Precondition Failed (One or more conditions in request failed).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
429 Response
Too Many Requests. Too many requests sent to the server in a short period.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
500 Response
Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
Default Response
Unknown Error. Error is not recognized by the system.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.