@databricks/sdk-warehouses 0.1.0-dev.3 → 0.1.0-dev.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/v1/model.d.ts +245 -236
- package/dist/v1/model.d.ts.map +1 -1
- package/dist/v1/model.js +266 -267
- package/dist/v1/model.js.map +1 -1
- package/dist/v1/utils.d.ts.map +1 -1
- package/dist/v1/utils.js +2 -1
- package/dist/v1/utils.js.map +1 -1
- package/package.json +4 -5
- package/src/v1/client.ts +0 -946
- package/src/v1/index.ts +0 -62
- package/src/v1/model.ts +0 -1997
- package/src/v1/transport.ts +0 -73
- package/src/v1/utils.ts +0 -180
package/dist/v1/model.d.ts
CHANGED
|
@@ -1,30 +1,33 @@
|
|
|
1
1
|
import { FieldMask } from '@databricks/sdk-core/wkt';
|
|
2
2
|
import { z } from 'zod';
|
|
3
|
-
export declare
|
|
4
|
-
CHANNEL_NAME_UNSPECIFIED
|
|
5
|
-
CHANNEL_NAME_PREVIEW
|
|
6
|
-
CHANNEL_NAME_CURRENT
|
|
7
|
-
CHANNEL_NAME_PREVIOUS
|
|
8
|
-
CHANNEL_NAME_CUSTOM
|
|
9
|
-
}
|
|
3
|
+
export declare const ChannelName: {
|
|
4
|
+
readonly CHANNEL_NAME_UNSPECIFIED: "CHANNEL_NAME_UNSPECIFIED";
|
|
5
|
+
readonly CHANNEL_NAME_PREVIEW: "CHANNEL_NAME_PREVIEW";
|
|
6
|
+
readonly CHANNEL_NAME_CURRENT: "CHANNEL_NAME_CURRENT";
|
|
7
|
+
readonly CHANNEL_NAME_PREVIOUS: "CHANNEL_NAME_PREVIOUS";
|
|
8
|
+
readonly CHANNEL_NAME_CUSTOM: "CHANNEL_NAME_CUSTOM";
|
|
9
|
+
};
|
|
10
|
+
export type ChannelName = (typeof ChannelName)[keyof typeof ChannelName] | (string & {});
|
|
10
11
|
/** Type of default warehouse override behavior. */
|
|
11
|
-
export declare
|
|
12
|
+
export declare const DefaultWarehouseOverrideType: {
|
|
12
13
|
/** Unspecified default warehouse override type. */
|
|
13
|
-
DEFAULT_WAREHOUSE_OVERRIDE_TYPE_UNSPECIFIED
|
|
14
|
+
readonly DEFAULT_WAREHOUSE_OVERRIDE_TYPE_UNSPECIFIED: "DEFAULT_WAREHOUSE_OVERRIDE_TYPE_UNSPECIFIED";
|
|
14
15
|
/** The user should remember their last-selected warehouse. */
|
|
15
|
-
LAST_SELECTED
|
|
16
|
+
readonly LAST_SELECTED: "LAST_SELECTED";
|
|
16
17
|
/** The user should use a specific warehouse. */
|
|
17
|
-
CUSTOM
|
|
18
|
-
}
|
|
18
|
+
readonly CUSTOM: "CUSTOM";
|
|
19
|
+
};
|
|
20
|
+
export type DefaultWarehouseOverrideType = (typeof DefaultWarehouseOverrideType)[keyof typeof DefaultWarehouseOverrideType] | (string & {});
|
|
19
21
|
/** Security policy to be used for warehouses */
|
|
20
|
-
export declare
|
|
22
|
+
export declare const EndpointSecurityPolicy: {
|
|
21
23
|
/** No passthrough or Table ACLs support */
|
|
22
|
-
NONE
|
|
24
|
+
readonly NONE: "NONE";
|
|
23
25
|
/** Support only Table ACLs */
|
|
24
|
-
DATA_ACCESS_CONTROL
|
|
26
|
+
readonly DATA_ACCESS_CONTROL: "DATA_ACCESS_CONTROL";
|
|
25
27
|
/** Support only ADLS / IAM passthrough */
|
|
26
|
-
PASSTHROUGH
|
|
27
|
-
}
|
|
28
|
+
readonly PASSTHROUGH: "PASSTHROUGH";
|
|
29
|
+
};
|
|
30
|
+
export type EndpointSecurityPolicy = (typeof EndpointSecurityPolicy)[keyof typeof EndpointSecurityPolicy] | (string & {});
|
|
28
31
|
/**
|
|
29
32
|
* EndpointSpotInstancePolicy configures whether the endpoint should use spot
|
|
30
33
|
* instances.
|
|
@@ -45,7 +48,7 @@ export declare enum EndpointSecurityPolicy {
|
|
|
45
48
|
* not", this is the field that PM recommends after discussion with customers
|
|
46
49
|
* per SC-48783.
|
|
47
50
|
*/
|
|
48
|
-
export declare
|
|
51
|
+
export declare const EndpointSpotInstancePolicy: {
|
|
49
52
|
/**
|
|
50
53
|
* UNSPECIFIED if no value is set by the caller.
|
|
51
54
|
* Consult endpoint docs to learn about the defaults that kick in if
|
|
@@ -66,56 +69,58 @@ export declare enum EndpointSpotInstancePolicy {
|
|
|
66
69
|
* This follows Google APIs:
|
|
67
70
|
* https://cloud.google.com/apis/design/design_patterns#enum_default_value.
|
|
68
71
|
*/
|
|
69
|
-
POLICY_UNSPECIFIED
|
|
72
|
+
readonly POLICY_UNSPECIFIED: "POLICY_UNSPECIFIED";
|
|
70
73
|
/** COST_OPTIMIZED to prefer spot instance. */
|
|
71
|
-
COST_OPTIMIZED
|
|
74
|
+
readonly COST_OPTIMIZED: "COST_OPTIMIZED";
|
|
72
75
|
/** RELIABILITY_OPTIMIZED to prefer on demand instance. */
|
|
73
|
-
RELIABILITY_OPTIMIZED
|
|
74
|
-
}
|
|
76
|
+
readonly RELIABILITY_OPTIMIZED: "RELIABILITY_OPTIMIZED";
|
|
77
|
+
};
|
|
78
|
+
export type EndpointSpotInstancePolicy = (typeof EndpointSpotInstancePolicy)[keyof typeof EndpointSpotInstancePolicy] | (string & {});
|
|
75
79
|
/**
|
|
76
80
|
* *
|
|
77
81
|
* State of a warehouse.
|
|
78
82
|
*/
|
|
79
|
-
export declare
|
|
83
|
+
export declare const EndpointState: {
|
|
80
84
|
/** Indicates that the endpoint is in the process of starting */
|
|
81
|
-
STARTING
|
|
85
|
+
readonly STARTING: "STARTING";
|
|
82
86
|
/** Indicates the starting process is done, and the endpoint is ready to use */
|
|
83
|
-
RUNNING
|
|
87
|
+
readonly RUNNING: "RUNNING";
|
|
84
88
|
/** Indicates the endpoint is in the process of destroying */
|
|
85
|
-
STOPPING
|
|
89
|
+
readonly STOPPING: "STOPPING";
|
|
86
90
|
/** Indicates the endpoint is stopped, but can be started by calling start */
|
|
87
|
-
STOPPED
|
|
91
|
+
readonly STOPPED: "STOPPED";
|
|
88
92
|
/** Indicates the endpoint is in the process of destroying */
|
|
89
|
-
DELETING
|
|
93
|
+
readonly DELETING: "DELETING";
|
|
90
94
|
/** Indicates an endpoint is deleted, and can not be recovered */
|
|
91
|
-
DELETED
|
|
92
|
-
}
|
|
95
|
+
readonly DELETED: "DELETED";
|
|
96
|
+
};
|
|
97
|
+
export type EndpointState = (typeof EndpointState)[keyof typeof EndpointState] | (string & {});
|
|
93
98
|
/** The status code indicating why the cluster was terminated */
|
|
94
|
-
export declare
|
|
99
|
+
export declare const TerminationCode: {
|
|
95
100
|
/** Default when there is no termination code. */
|
|
96
|
-
UNKNOWN
|
|
101
|
+
readonly UNKNOWN: "UNKNOWN";
|
|
97
102
|
/**
|
|
98
103
|
* A user terminated the cluster directly. Parameters should include a ``username`` field
|
|
99
104
|
* that indicates the specific user who terminated the cluster.
|
|
100
105
|
*/
|
|
101
|
-
USER_REQUEST
|
|
106
|
+
readonly USER_REQUEST: "USER_REQUEST";
|
|
102
107
|
/** This cluster was launched by a Job, and terminated when the Job completed. */
|
|
103
|
-
JOB_FINISHED
|
|
108
|
+
readonly JOB_FINISHED: "JOB_FINISHED";
|
|
104
109
|
/** This cluster was terminated since it was idle. */
|
|
105
|
-
INACTIVITY
|
|
110
|
+
readonly INACTIVITY: "INACTIVITY";
|
|
106
111
|
/**
|
|
107
112
|
* The instance that hosted the spark driver was terminated by the cloud provider. In AWS, for
|
|
108
113
|
* example, AWS may retire instances and directly shut them down.
|
|
109
114
|
* Parameters should include an ``aws_instance_state_reason`` field indicating the AWS-provided
|
|
110
115
|
* reason why the instance was terminated.
|
|
111
116
|
*/
|
|
112
|
-
CLOUD_PROVIDER_SHUTDOWN
|
|
117
|
+
readonly CLOUD_PROVIDER_SHUTDOWN: "CLOUD_PROVIDER_SHUTDOWN";
|
|
113
118
|
/**
|
|
114
119
|
* Databricks may lose connection to services on the driver instance. One such case is when
|
|
115
120
|
* problems arise in cloud networking infrastructure, or when the instance itself becomes
|
|
116
121
|
* unhealthy.
|
|
117
122
|
*/
|
|
118
|
-
COMMUNICATION_LOST
|
|
123
|
+
readonly COMMUNICATION_LOST: "COMMUNICATION_LOST";
|
|
119
124
|
/**
|
|
120
125
|
* Databricks may hit cloud provider failures when requesting instances to launch clusters.
|
|
121
126
|
* For example, AWS limits the number of running instances and EBS volumes. If you ask Databricks
|
|
@@ -125,61 +130,61 @@ export declare enum TerminationCode {
|
|
|
125
130
|
* ``aws_spot_request_status`` to indicate the AWS-provided reason why Databricks could not
|
|
126
131
|
* request the required instances for the cluster.
|
|
127
132
|
*/
|
|
128
|
-
CLOUD_PROVIDER_LAUNCH_FAILURE
|
|
133
|
+
readonly CLOUD_PROVIDER_LAUNCH_FAILURE: "CLOUD_PROVIDER_LAUNCH_FAILURE";
|
|
129
134
|
/**
|
|
130
135
|
* Databricks cannot load and execute a cluster-scoped init script on one of the cluster's nodes,
|
|
131
136
|
* or the init script terminates with a non-zero exit code or there was a general failure during
|
|
132
137
|
* the loading/executing of init scripts that does not pertain to any specific script.
|
|
133
138
|
*/
|
|
134
|
-
INIT_SCRIPT_FAILURE
|
|
139
|
+
readonly INIT_SCRIPT_FAILURE: "INIT_SCRIPT_FAILURE";
|
|
135
140
|
/**
|
|
136
141
|
* The Spark driver failed to start. Possible reasons may include incompatible libraries and
|
|
137
142
|
* initialization scripts that corrupted the Spark container.
|
|
138
143
|
*/
|
|
139
|
-
SPARK_STARTUP_FAILURE
|
|
144
|
+
readonly SPARK_STARTUP_FAILURE: "SPARK_STARTUP_FAILURE";
|
|
140
145
|
/**
|
|
141
146
|
* Cannot launch the cluster because the user specified an invalid argument. For example,
|
|
142
147
|
* the use might specify an invalid spark version for the cluster.
|
|
143
148
|
*/
|
|
144
|
-
INVALID_ARGUMENT
|
|
149
|
+
readonly INVALID_ARGUMENT: "INVALID_ARGUMENT";
|
|
145
150
|
/**
|
|
146
151
|
* While launching this cluster, Databricks failed to complete critical setup steps, terminating
|
|
147
152
|
* the cluster.
|
|
148
153
|
*/
|
|
149
|
-
UNEXPECTED_LAUNCH_FAILURE
|
|
154
|
+
readonly UNEXPECTED_LAUNCH_FAILURE: "UNEXPECTED_LAUNCH_FAILURE";
|
|
150
155
|
/**
|
|
151
156
|
* Databricks encountered an unexpected error which forced the running cluster to be terminated.
|
|
152
157
|
* Please contact Databricks support for additional details.
|
|
153
158
|
*/
|
|
154
|
-
INTERNAL_ERROR
|
|
159
|
+
readonly INTERNAL_ERROR: "INTERNAL_ERROR";
|
|
155
160
|
/**
|
|
156
161
|
* Databricks was not able to access instances in order to start the cluster. This can be a
|
|
157
162
|
* transient networking issue. If the problem persists, this usually indicates a networking
|
|
158
163
|
* environment misconfiguration.
|
|
159
164
|
*/
|
|
160
|
-
INSTANCE_UNREACHABLE
|
|
165
|
+
readonly INSTANCE_UNREACHABLE: "INSTANCE_UNREACHABLE";
|
|
161
166
|
/**
|
|
162
167
|
* Blocked upsize requests for the workspace according to
|
|
163
168
|
* https://databricks.atlassian.net/wiki/spaces/UN/pages/934088320/Banning+Workspace+Upsize+Runbook
|
|
164
169
|
*/
|
|
165
|
-
REQUEST_REJECTED
|
|
170
|
+
readonly REQUEST_REJECTED: "REQUEST_REJECTED";
|
|
166
171
|
/** The cluster was terminated because it was running in a trial workspace that expired. */
|
|
167
|
-
TRIAL_EXPIRED
|
|
172
|
+
readonly TRIAL_EXPIRED: "TRIAL_EXPIRED";
|
|
168
173
|
/**
|
|
169
174
|
* The cluster was terminated because no response from the chauffeur could be received. We name
|
|
170
175
|
* this "DRIVER_" instead of "CHAUFFEUR_" since chauffeur is non-external terminology
|
|
171
176
|
*/
|
|
172
|
-
DRIVER_UNREACHABLE
|
|
177
|
+
readonly DRIVER_UNREACHABLE: "DRIVER_UNREACHABLE";
|
|
173
178
|
/** Spark error on startup */
|
|
174
|
-
SPARK_ERROR
|
|
179
|
+
readonly SPARK_ERROR: "SPARK_ERROR";
|
|
175
180
|
/** Driver unresponsive */
|
|
176
|
-
DRIVER_UNRESPONSIVE
|
|
181
|
+
readonly DRIVER_UNRESPONSIVE: "DRIVER_UNRESPONSIVE";
|
|
177
182
|
/** Metastore component unhealthy */
|
|
178
|
-
METASTORE_COMPONENT_UNHEALTHY
|
|
183
|
+
readonly METASTORE_COMPONENT_UNHEALTHY: "METASTORE_COMPONENT_UNHEALTHY";
|
|
179
184
|
/** DBFS component unhealthy */
|
|
180
|
-
DBFS_COMPONENT_UNHEALTHY
|
|
185
|
+
readonly DBFS_COMPONENT_UNHEALTHY: "DBFS_COMPONENT_UNHEALTHY";
|
|
181
186
|
/** Execution component unhealthy */
|
|
182
|
-
EXECUTION_COMPONENT_UNHEALTHY
|
|
187
|
+
readonly EXECUTION_COMPONENT_UNHEALTHY: "EXECUTION_COMPONENT_UNHEALTHY";
|
|
183
188
|
/**
|
|
184
189
|
* Databricks may hit the azure resource manager request limit. Which will keep the Azure SDK
|
|
185
190
|
* from issuing any read or write request to Azure resource manager. The request limit is applied
|
|
@@ -187,7 +192,7 @@ export declare enum TerminationCode {
|
|
|
187
192
|
* might help to resolve the issue. Please check the following link for more information:
|
|
188
193
|
* https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-request-limits
|
|
189
194
|
*/
|
|
190
|
-
AZURE_RESOURCE_MANAGER_THROTTLING
|
|
195
|
+
readonly AZURE_RESOURCE_MANAGER_THROTTLING: "AZURE_RESOURCE_MANAGER_THROTTLING";
|
|
191
196
|
/**
|
|
192
197
|
* Databricks may hit the azure resource provider request limit. Specifically, the API request
|
|
193
198
|
* rate to the specific resource type (Compute, Network, etc..) can't exceed the limit. Retry
|
|
@@ -195,146 +200,146 @@ export declare enum TerminationCode {
|
|
|
195
200
|
* https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/
|
|
196
201
|
* troubleshooting-throttling-errors
|
|
197
202
|
*/
|
|
198
|
-
AZURE_RESOURCE_PROVIDER_THROTTLING
|
|
203
|
+
readonly AZURE_RESOURCE_PROVIDER_THROTTLING: "AZURE_RESOURCE_PROVIDER_THROTTLING";
|
|
199
204
|
/** The cluster was terminated due to an error in the network configuration. */
|
|
200
|
-
NETWORK_CONFIGURATION_FAILURE
|
|
205
|
+
readonly NETWORK_CONFIGURATION_FAILURE: "NETWORK_CONFIGURATION_FAILURE";
|
|
201
206
|
/**
|
|
202
207
|
* Databricks encountered an unexpected error while launching containers on worker nodes for the
|
|
203
208
|
* cluster, terminating the cluster.
|
|
204
209
|
*/
|
|
205
|
-
CONTAINER_LAUNCH_FAILURE
|
|
210
|
+
readonly CONTAINER_LAUNCH_FAILURE: "CONTAINER_LAUNCH_FAILURE";
|
|
206
211
|
/** Instance pool backed cluster specific failure */
|
|
207
|
-
INSTANCE_POOL_CLUSTER_FAILURE
|
|
212
|
+
readonly INSTANCE_POOL_CLUSTER_FAILURE: "INSTANCE_POOL_CLUSTER_FAILURE";
|
|
208
213
|
/** Cluster start successfully completed but skipped some instances which were slow to launch */
|
|
209
|
-
SKIPPED_SLOW_NODES
|
|
214
|
+
readonly SKIPPED_SLOW_NODES: "SKIPPED_SLOW_NODES";
|
|
210
215
|
/** Attach projects failure */
|
|
211
|
-
ATTACH_PROJECT_FAILURE
|
|
216
|
+
readonly ATTACH_PROJECT_FAILURE: "ATTACH_PROJECT_FAILURE";
|
|
212
217
|
/** Attach projects failure */
|
|
213
|
-
UPDATE_INSTANCE_PROFILE_FAILURE
|
|
218
|
+
readonly UPDATE_INSTANCE_PROFILE_FAILURE: "UPDATE_INSTANCE_PROFILE_FAILURE";
|
|
214
219
|
/** Cluster terminated due to database failure */
|
|
215
|
-
DATABASE_CONNECTION_FAILURE
|
|
220
|
+
readonly DATABASE_CONNECTION_FAILURE: "DATABASE_CONNECTION_FAILURE";
|
|
216
221
|
/**
|
|
217
222
|
* Databricks cannot handle the request at this moment. Please try again later
|
|
218
223
|
* and contact Databricks if the problem persists.
|
|
219
224
|
*/
|
|
220
|
-
REQUEST_THROTTLED
|
|
225
|
+
readonly REQUEST_THROTTLED: "REQUEST_THROTTLED";
|
|
221
226
|
/** SelfBootstrap failure. Either self-bootstrap fast fail or node daemon ping timeout */
|
|
222
|
-
SELF_BOOTSTRAP_FAILURE
|
|
227
|
+
readonly SELF_BOOTSTRAP_FAILURE: "SELF_BOOTSTRAP_FAILURE";
|
|
223
228
|
/**
|
|
224
229
|
* Databricks cannot load and execute a global init script on one of the cluster's nodes,
|
|
225
230
|
* or the init script terminates with a non-zero exit code.
|
|
226
231
|
*/
|
|
227
|
-
GLOBAL_INIT_SCRIPT_FAILURE
|
|
232
|
+
readonly GLOBAL_INIT_SCRIPT_FAILURE: "GLOBAL_INIT_SCRIPT_FAILURE";
|
|
228
233
|
/**
|
|
229
234
|
* Container launch timed out downloading the spark image. This can happen if the customer
|
|
230
235
|
* has byo-vpc/vnet and the download of large files is being throttled.
|
|
231
236
|
*/
|
|
232
|
-
SLOW_IMAGE_DOWNLOAD
|
|
237
|
+
readonly SLOW_IMAGE_DOWNLOAD: "SLOW_IMAGE_DOWNLOAD";
|
|
233
238
|
/** Container setup failed due to an invalid Spark image. */
|
|
234
|
-
INVALID_SPARK_IMAGE
|
|
239
|
+
readonly INVALID_SPARK_IMAGE: "INVALID_SPARK_IMAGE";
|
|
235
240
|
/**
|
|
236
241
|
* If the ngrok tunnel token provisioning fails for any reason, for example hitting the
|
|
237
242
|
* max capacity of allowed ngrok tokens. (ES-32083)
|
|
238
243
|
*/
|
|
239
|
-
NPIP_TUNNEL_TOKEN_FAILURE
|
|
244
|
+
readonly NPIP_TUNNEL_TOKEN_FAILURE: "NPIP_TUNNEL_TOKEN_FAILURE";
|
|
240
245
|
/** Hive Metastore provisioning failue in launch container step */
|
|
241
|
-
HIVE_METASTORE_PROVISIONING_FAILURE
|
|
246
|
+
readonly HIVE_METASTORE_PROVISIONING_FAILURE: "HIVE_METASTORE_PROVISIONING_FAILURE";
|
|
242
247
|
/**
|
|
243
248
|
* Occurs when the deployment template we submit to Azure violates their requirements.
|
|
244
249
|
* Typical scenarios:
|
|
245
250
|
* - Wrong parameter key/value used
|
|
246
251
|
* - Exceed the limit for certain parameter
|
|
247
252
|
*/
|
|
248
|
-
AZURE_INVALID_DEPLOYMENT_TEMPLATE
|
|
253
|
+
readonly AZURE_INVALID_DEPLOYMENT_TEMPLATE: "AZURE_INVALID_DEPLOYMENT_TEMPLATE";
|
|
249
254
|
/**
|
|
250
255
|
* The set of un-categorized failure responses from Azure when we launch instance resources
|
|
251
256
|
* using deployment template
|
|
252
257
|
*/
|
|
253
|
-
AZURE_UNEXPECTED_DEPLOYMENT_TEMPLATE_FAILURE
|
|
258
|
+
readonly AZURE_UNEXPECTED_DEPLOYMENT_TEMPLATE_FAILURE: "AZURE_UNEXPECTED_DEPLOYMENT_TEMPLATE_FAILURE";
|
|
254
259
|
/** Subnet (typically Azure vnet injected) has run out of ip addresses */
|
|
255
|
-
SUBNET_EXHAUSTED_FAILURE
|
|
260
|
+
readonly SUBNET_EXHAUSTED_FAILURE: "SUBNET_EXHAUSTED_FAILURE";
|
|
256
261
|
/**
|
|
257
262
|
* Timeout to ping the nodeDaemon, possible reason: nodeDaemon didn't start (configuration issue),
|
|
258
263
|
* network connectivity issue
|
|
259
264
|
*/
|
|
260
|
-
BOOTSTRAP_TIMEOUT
|
|
265
|
+
readonly BOOTSTRAP_TIMEOUT: "BOOTSTRAP_TIMEOUT";
|
|
261
266
|
/** Bootstrap timeout due to script download failure */
|
|
262
|
-
STORAGE_DOWNLOAD_FAILURE
|
|
267
|
+
readonly STORAGE_DOWNLOAD_FAILURE: "STORAGE_DOWNLOAD_FAILURE";
|
|
263
268
|
/** Bootstrap timeout due to get runbook failure */
|
|
264
|
-
CONTROL_PLANE_REQUEST_FAILURE
|
|
269
|
+
readonly CONTROL_PLANE_REQUEST_FAILURE: "CONTROL_PLANE_REQUEST_FAILURE";
|
|
265
270
|
/** Bootstrap timeout due to Azure Extension Service Failure */
|
|
266
|
-
BOOTSTRAP_TIMEOUT_CLOUD_PROVIDER_EXCEPTION
|
|
271
|
+
readonly BOOTSTRAP_TIMEOUT_CLOUD_PROVIDER_EXCEPTION: "BOOTSTRAP_TIMEOUT_CLOUD_PROVIDER_EXCEPTION";
|
|
267
272
|
/** Could not find enough of the requested instance type in the requested AZ. Often related to Auto AZ. */
|
|
268
|
-
AWS_INSUFFICIENT_INSTANCE_CAPACITY_FAILURE
|
|
273
|
+
readonly AWS_INSUFFICIENT_INSTANCE_CAPACITY_FAILURE: "AWS_INSUFFICIENT_INSTANCE_CAPACITY_FAILURE";
|
|
269
274
|
/** Container setup failure due to docker image pulling failure */
|
|
270
|
-
DOCKER_IMAGE_PULL_FAILURE
|
|
275
|
+
readonly DOCKER_IMAGE_PULL_FAILURE: "DOCKER_IMAGE_PULL_FAILURE";
|
|
271
276
|
/**
|
|
272
277
|
* Failures during azure vnet configuration. For example, a workspace with VNet injection had
|
|
273
278
|
* incorrect DNS settings that blocked access to worker artifacts.
|
|
274
279
|
*/
|
|
275
|
-
AZURE_VNET_CONFIGURATION_FAILURE
|
|
280
|
+
readonly AZURE_VNET_CONFIGURATION_FAILURE: "AZURE_VNET_CONFIGURATION_FAILURE";
|
|
276
281
|
/**
|
|
277
282
|
* Bootstrap failure due to Ngrok tunnel setup timeout or failure. For example, if the worker
|
|
278
283
|
* node is unable to reach the Ngrok tunnel domain.
|
|
279
284
|
*/
|
|
280
|
-
NPIP_TUNNEL_SETUP_FAILURE
|
|
285
|
+
readonly NPIP_TUNNEL_SETUP_FAILURE: "NPIP_TUNNEL_SETUP_FAILURE";
|
|
281
286
|
/**
|
|
282
287
|
* Lack authorization for cluster operation.
|
|
283
288
|
* For example, awsApiErrorCode: 'AccessDenied' or 'UnauthorizedOperation'.
|
|
284
289
|
*/
|
|
285
|
-
AWS_AUTHORIZATION_FAILURE
|
|
290
|
+
readonly AWS_AUTHORIZATION_FAILURE: "AWS_AUTHORIZATION_FAILURE";
|
|
286
291
|
/** request comes form Nephos resource pool auto management */
|
|
287
|
-
NEPHOS_RESOURCE_MANAGEMENT
|
|
292
|
+
readonly NEPHOS_RESOURCE_MANAGEMENT: "NEPHOS_RESOURCE_MANAGEMENT";
|
|
288
293
|
/**
|
|
289
294
|
* Container setup failed during container registration to security daemon due to STS endpoint
|
|
290
295
|
* connection error.
|
|
291
296
|
*/
|
|
292
|
-
STS_CLIENT_SETUP_FAILURE
|
|
297
|
+
readonly STS_CLIENT_SETUP_FAILURE: "STS_CLIENT_SETUP_FAILURE";
|
|
293
298
|
/** Container setup failed during registration to security daemon due to an unspecified error. */
|
|
294
|
-
SECURITY_DAEMON_REGISTRATION_EXCEPTION
|
|
299
|
+
readonly SECURITY_DAEMON_REGISTRATION_EXCEPTION: "SECURITY_DAEMON_REGISTRATION_EXCEPTION";
|
|
295
300
|
/** The maximum request rate permitted by the Amazon EC2 APIs has been exceeded for your account. */
|
|
296
|
-
AWS_REQUEST_LIMIT_EXCEEDED
|
|
301
|
+
readonly AWS_REQUEST_LIMIT_EXCEEDED: "AWS_REQUEST_LIMIT_EXCEEDED";
|
|
297
302
|
/** We don't have enough addresses in the subnet for the instances in the request. */
|
|
298
|
-
AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE
|
|
303
|
+
readonly AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE: "AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE";
|
|
299
304
|
/** The request is not supported (This is a vague error code that can be thrown for a lot of reasons.) */
|
|
300
|
-
AWS_UNSUPPORTED_FAILURE
|
|
305
|
+
readonly AWS_UNSUPPORTED_FAILURE: "AWS_UNSUPPORTED_FAILURE";
|
|
301
306
|
/** Could not find enough azure resources to fulfill the request. */
|
|
302
|
-
AZURE_QUOTA_EXCEEDED_EXCEPTION
|
|
307
|
+
readonly AZURE_QUOTA_EXCEEDED_EXCEPTION: "AZURE_QUOTA_EXCEEDED_EXCEPTION";
|
|
303
308
|
/** NOTE: This is currently used by exceptions with messages that are classified as user errors. */
|
|
304
|
-
AZURE_OPERATION_NOT_ALLOWED_EXCEPTION
|
|
309
|
+
readonly AZURE_OPERATION_NOT_ALLOWED_EXCEPTION: "AZURE_OPERATION_NOT_ALLOWED_EXCEPTION";
|
|
305
310
|
/** Failure when mounting remote NFS to container */
|
|
306
|
-
NFS_MOUNT_FAILURE
|
|
311
|
+
readonly NFS_MOUNT_FAILURE: "NFS_MOUNT_FAILURE";
|
|
307
312
|
/** K8S failed to upscale to acquire new nodes */
|
|
308
|
-
K8S_AUTOSCALING_FAILURE
|
|
313
|
+
readonly K8S_AUTOSCALING_FAILURE: "K8S_AUTOSCALING_FAILURE";
|
|
309
314
|
/** DBR Cluster launched on K8s (i.e. CMv2) has failed to start up in time */
|
|
310
|
-
K8S_DBR_CLUSTER_LAUNCH_TIMEOUT
|
|
315
|
+
readonly K8S_DBR_CLUSTER_LAUNCH_TIMEOUT: "K8S_DBR_CLUSTER_LAUNCH_TIMEOUT";
|
|
311
316
|
/**
|
|
312
317
|
* Container launch failed while downloading the spark image. Catch all for if anything
|
|
313
318
|
* goes wrong while downloading and extracting the spark tarball.
|
|
314
319
|
*/
|
|
315
|
-
SPARK_IMAGE_DOWNLOAD_FAILURE
|
|
320
|
+
readonly SPARK_IMAGE_DOWNLOAD_FAILURE: "SPARK_IMAGE_DOWNLOAD_FAILURE";
|
|
316
321
|
/** Azure VM Extension failure during instance bootstrap */
|
|
317
|
-
AZURE_VM_EXTENSION_FAILURE
|
|
322
|
+
readonly AZURE_VM_EXTENSION_FAILURE: "AZURE_VM_EXTENSION_FAILURE";
|
|
318
323
|
/** Workspace was cancelled hence deny/terminate the cluster */
|
|
319
|
-
WORKSPACE_CANCELLED_ERROR
|
|
324
|
+
readonly WORKSPACE_CANCELLED_ERROR: "WORKSPACE_CANCELLED_ERROR";
|
|
320
325
|
/** The spot instance count in an account has exceeded the limit */
|
|
321
|
-
AWS_MAX_SPOT_INSTANCE_COUNT_EXCEEDED_FAILURE
|
|
326
|
+
readonly AWS_MAX_SPOT_INSTANCE_COUNT_EXCEEDED_FAILURE: "AWS_MAX_SPOT_INSTANCE_COUNT_EXCEEDED_FAILURE";
|
|
322
327
|
/**
|
|
323
328
|
* Cluster is terminated because the services are temporarily unavailable.
|
|
324
329
|
* This normally happens when CM is restarting and draining execution contexts,
|
|
325
330
|
* or IM/Delegate is overloaded, so that it will not be able to retry the instance launch request.
|
|
326
331
|
*/
|
|
327
|
-
TEMPORARILY_UNAVAILABLE
|
|
332
|
+
readonly TEMPORARILY_UNAVAILABLE: "TEMPORARILY_UNAVAILABLE";
|
|
328
333
|
/**
|
|
329
334
|
* Bootstrap failure due to error during worker setup, usually due to an issue with
|
|
330
335
|
* disk or gpu setup. See SetupCommandBuilder for other possible causes
|
|
331
336
|
*/
|
|
332
|
-
WORKER_SETUP_FAILURE
|
|
337
|
+
readonly WORKER_SETUP_FAILURE: "WORKER_SETUP_FAILURE";
|
|
333
338
|
/**
|
|
334
339
|
* Cluster failure due to IP space exhaustion. For example on CMv2, Kubernetes will fail to scale
|
|
335
340
|
* up new nodes if the pod IP CIDR block is exhausted.
|
|
336
341
|
*/
|
|
337
|
-
IP_EXHAUSTION_FAILURE
|
|
342
|
+
readonly IP_EXHAUSTION_FAILURE: "IP_EXHAUSTION_FAILURE";
|
|
338
343
|
/**
|
|
339
344
|
* Could not find enough GCP resources to fulfill the request.
|
|
340
345
|
* TODO: It's very unfortunate that we have per-cloud termination reasons while we should have
|
|
@@ -342,101 +347,101 @@ export declare enum TerminationCode {
|
|
|
342
347
|
* {AZURE_QUOTA_EXCEEDED_EXCEPTION, AWS_REQUEST_LIMIT_EXCEEDED and GCP_QUOTA_EXCEEDED},
|
|
343
348
|
* {AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE, IP_EXHAUSTION_FAILURE}, etc.
|
|
344
349
|
*/
|
|
345
|
-
GCP_QUOTA_EXCEEDED
|
|
350
|
+
readonly GCP_QUOTA_EXCEEDED: "GCP_QUOTA_EXCEEDED";
|
|
346
351
|
/** Cloud provider is undergoing a transient resource throttling. This is retryable. */
|
|
347
|
-
CLOUD_PROVIDER_RESOURCE_STOCKOUT
|
|
352
|
+
readonly CLOUD_PROVIDER_RESOURCE_STOCKOUT: "CLOUD_PROVIDER_RESOURCE_STOCKOUT";
|
|
348
353
|
/** The GCP service account associated with the DBR cluster is deleted. */
|
|
349
|
-
GCP_SERVICE_ACCOUNT_DELETED
|
|
354
|
+
readonly GCP_SERVICE_ACCOUNT_DELETED: "GCP_SERVICE_ACCOUNT_DELETED";
|
|
350
355
|
/** Legit cluster termination in Azure caused by customer revoking the key permission used for managed-disks encryption */
|
|
351
|
-
AZURE_BYOK_KEY_PERMISSION_FAILURE
|
|
356
|
+
readonly AZURE_BYOK_KEY_PERMISSION_FAILURE: "AZURE_BYOK_KEY_PERMISSION_FAILURE";
|
|
352
357
|
/** Termination because of spot instance terminated by cloud provider */
|
|
353
|
-
SPOT_INSTANCE_TERMINATION
|
|
358
|
+
readonly SPOT_INSTANCE_TERMINATION: "SPOT_INSTANCE_TERMINATION";
|
|
354
359
|
/** Termination because of unsupported azure ephemeral os disk setup */
|
|
355
|
-
AZURE_EPHEMERAL_DISK_FAILURE
|
|
360
|
+
readonly AZURE_EPHEMERAL_DISK_FAILURE: "AZURE_EPHEMERAL_DISK_FAILURE";
|
|
356
361
|
/**
|
|
357
362
|
* The cluster was terminated because we detected an abusive runtime behavior that violated
|
|
358
363
|
* Terms of Service or Acceptable Use Policy.
|
|
359
364
|
*/
|
|
360
|
-
ABUSE_DETECTED
|
|
365
|
+
readonly ABUSE_DETECTED: "ABUSE_DETECTED";
|
|
361
366
|
/** Failed to pull DBR images due to permission error. */
|
|
362
|
-
IMAGE_PULL_PERMISSION_DENIED
|
|
367
|
+
readonly IMAGE_PULL_PERMISSION_DENIED: "IMAGE_PULL_PERMISSION_DENIED";
|
|
363
368
|
/** Workspace configuration is in error state due to configuration issue or ACL modification by the customer side */
|
|
364
|
-
WORKSPACE_CONFIGURATION_ERROR
|
|
369
|
+
readonly WORKSPACE_CONFIGURATION_ERROR: "WORKSPACE_CONFIGURATION_ERROR";
|
|
365
370
|
/**
|
|
366
371
|
* Catch all error for all secret resolution issues in cluster launch. This should be alerted on,
|
|
367
372
|
* and is considered a server error. This can be split out into other cases if there are client
|
|
368
373
|
* errors - for e.g. INVALID_ARGUMENT is used for secrets that don't exist and permission issues
|
|
369
374
|
*/
|
|
370
|
-
SECRET_RESOLUTION_ERROR
|
|
375
|
+
readonly SECRET_RESOLUTION_ERROR: "SECRET_RESOLUTION_ERROR";
|
|
371
376
|
/**
|
|
372
377
|
* Failure due to an instance being of an unsupported type. This is used when an instance in
|
|
373
378
|
* an EC2 fleet is of an unrecognized type, or an invalid type (i.e. graviton when we don't
|
|
374
379
|
* want graviton instances). This should be alerted on.
|
|
375
380
|
*/
|
|
376
|
-
UNSUPPORTED_INSTANCE_TYPE
|
|
381
|
+
readonly UNSUPPORTED_INSTANCE_TYPE: "UNSUPPORTED_INSTANCE_TYPE";
|
|
377
382
|
/** Failed during instance bootstrap with error code Cannot convert NVMe-based dev id */
|
|
378
|
-
CLOUD_PROVIDER_DISK_SETUP_FAILURE
|
|
383
|
+
readonly CLOUD_PROVIDER_DISK_SETUP_FAILURE: "CLOUD_PROVIDER_DISK_SETUP_FAILURE";
|
|
379
384
|
/** Exception when setting up instances using ssh bootstrap */
|
|
380
|
-
SSH_BOOTSTRAP_FAILURE
|
|
385
|
+
readonly SSH_BOOTSTRAP_FAILURE: "SSH_BOOTSTRAP_FAILURE";
|
|
381
386
|
/** Failed during instance bootstrap with error code Cannot convert NVMe-based dev id */
|
|
382
|
-
AWS_INACCESSIBLE_KMS_KEY_FAILURE
|
|
387
|
+
readonly AWS_INACCESSIBLE_KMS_KEY_FAILURE: "AWS_INACCESSIBLE_KMS_KEY_FAILURE";
|
|
383
388
|
/**
|
|
384
389
|
* The bootstrapping init-containers in Spark failed or timed out, blocking the Spark container
|
|
385
390
|
* from bootstrapping. This is a refinement of `SPARK_STARTUP_FAILURE`.
|
|
386
391
|
* (init-containers are a bootstrapping step owned by Databricks)
|
|
387
392
|
*/
|
|
388
|
-
INIT_CONTAINER_NOT_FINISHED
|
|
393
|
+
readonly INIT_CONTAINER_NOT_FINISHED: "INIT_CONTAINER_NOT_FINISHED";
|
|
389
394
|
/**
|
|
390
395
|
* Container launch failed due to storage servers throttling our download of spark images. Can
|
|
391
396
|
* happen due to transient spikes of downloads overloading storage servers or gradual increase in
|
|
392
397
|
* usage. In the latter case we need to increase the number of storage servers in the region to
|
|
393
398
|
* help spread load.
|
|
394
399
|
*/
|
|
395
|
-
SPARK_IMAGE_DOWNLOAD_THROTTLED
|
|
400
|
+
readonly SPARK_IMAGE_DOWNLOAD_THROTTLED: "SPARK_IMAGE_DOWNLOAD_THROTTLED";
|
|
396
401
|
/**
|
|
397
402
|
* The spark image specified for the cluster was not found when attempting to download. Usually
|
|
398
403
|
* due to the customer custom specifying a bad image.
|
|
399
404
|
*/
|
|
400
|
-
SPARK_IMAGE_NOT_FOUND
|
|
405
|
+
readonly SPARK_IMAGE_NOT_FOUND: "SPARK_IMAGE_NOT_FOUND";
|
|
401
406
|
/**
|
|
402
407
|
* Indicates that the cloud provider operations performed for the cluster were dropped due to
|
|
403
408
|
* an influx in load in the cloud provider and had to be dropped from our end to alleviate
|
|
404
409
|
* pressure within the DelegateRpcClient. Please see go/cmloadshedding for more.
|
|
405
410
|
*/
|
|
406
|
-
CLUSTER_OPERATION_THROTTLED
|
|
411
|
+
readonly CLUSTER_OPERATION_THROTTLED: "CLUSTER_OPERATION_THROTTLED";
|
|
407
412
|
/**
|
|
408
413
|
* The error code can be used to indicate a request misses its deadline. Can be used for either request timeouts
|
|
409
414
|
* or missed deadlines (i.e. a request is not completed as it was processed after its specified deadline)
|
|
410
415
|
*/
|
|
411
|
-
CLUSTER_OPERATION_TIMEOUT
|
|
416
|
+
readonly CLUSTER_OPERATION_TIMEOUT: "CLUSTER_OPERATION_TIMEOUT";
|
|
412
417
|
/**
|
|
413
418
|
* This error code is used to terminate long-running Generic compute jobs in Serverless Environment
|
|
414
419
|
* as part of the NephosLongRunning watcher running in Cluster Monitor Service.
|
|
415
420
|
*/
|
|
416
|
-
SERVERLESS_LONG_RUNNING_TERMINATED
|
|
421
|
+
readonly SERVERLESS_LONG_RUNNING_TERMINATED: "SERVERLESS_LONG_RUNNING_TERMINATED";
|
|
417
422
|
/**
|
|
418
423
|
* This error code is used when the cluster is terminated due to its instances fail with partial failure from Azure
|
|
419
424
|
* packed deployments. In Azure, we might pack multiple launch requests in one deployment template in order
|
|
420
425
|
* to avoid the 800 templates limit on Azure side. If the packed deployment fails multiple times, the cluster could
|
|
421
426
|
* be terminated by this [[AZURE_PACKED_DEPLOYMENT_PARTIAL_FAILURE]] termination code.
|
|
422
427
|
*/
|
|
423
|
-
AZURE_PACKED_DEPLOYMENT_PARTIAL_FAILURE
|
|
428
|
+
readonly AZURE_PACKED_DEPLOYMENT_PARTIAL_FAILURE: "AZURE_PACKED_DEPLOYMENT_PARTIAL_FAILURE";
|
|
424
429
|
/**
|
|
425
430
|
* The instances acquired from a pool in IMv2 do not have a valid worker image to be used in the
|
|
426
431
|
* cluster launch. This usually occurs after AMI/VHD upgrades, worker branch updates, etc.
|
|
427
432
|
*/
|
|
428
|
-
INVALID_WORKER_IMAGE_FAILURE
|
|
433
|
+
readonly INVALID_WORKER_IMAGE_FAILURE: "INVALID_WORKER_IMAGE_FAILURE";
|
|
429
434
|
/** Worker environment version was changed due to workspace network or CMK update. */
|
|
430
|
-
WORKSPACE_UPDATE
|
|
435
|
+
readonly WORKSPACE_UPDATE: "WORKSPACE_UPDATE";
|
|
431
436
|
/** The parameter user specified or the user account to create the cluster is invalid according to AWS. */
|
|
432
|
-
INVALID_AWS_PARAMETER
|
|
437
|
+
readonly INVALID_AWS_PARAMETER: "INVALID_AWS_PARAMETER";
|
|
433
438
|
/**
|
|
434
439
|
* ** Only relevant on k8s dataplanes (i.e. clusters launched with CMv2 - not CMv1).
|
|
435
440
|
*
|
|
436
441
|
* k8s evicted the driver pod due to disk pressure on the driver node. This is likely due to a
|
|
437
442
|
* customer job consuming too much disk and so this is classified as a customer issue.
|
|
438
443
|
*/
|
|
439
|
-
DRIVER_OUT_OF_DISK
|
|
444
|
+
readonly DRIVER_OUT_OF_DISK: "DRIVER_OUT_OF_DISK";
|
|
440
445
|
/**
|
|
441
446
|
* ** Only relevant on k8s dataplanes (i.e. clusters launched with CMv2 - not CMv1).
|
|
442
447
|
*
|
|
@@ -445,244 +450,248 @@ export declare enum TerminationCode {
|
|
|
445
450
|
* OOM first (we set memory limits on our pods). Thus this termination reason will be considered
|
|
446
451
|
* a databricks issue.
|
|
447
452
|
*/
|
|
448
|
-
DRIVER_OUT_OF_MEMORY
|
|
453
|
+
readonly DRIVER_OUT_OF_MEMORY: "DRIVER_OUT_OF_MEMORY";
|
|
449
454
|
/**
|
|
450
455
|
* ** Only relevant on k8s dataplanes (i.e. clusters launched with CMv2 - not CMv1).
|
|
451
456
|
* Original driver pod took too long to become ready and timed out.
|
|
452
457
|
*/
|
|
453
|
-
DRIVER_LAUNCH_TIMEOUT
|
|
458
|
+
readonly DRIVER_LAUNCH_TIMEOUT: "DRIVER_LAUNCH_TIMEOUT";
|
|
454
459
|
/**
|
|
455
460
|
* ** Only relevant on k8s dataplanes (i.e. clusters launched with CMv2 - not CMv1).
|
|
456
461
|
* Unexpected failure during driver pod launch.
|
|
457
462
|
*/
|
|
458
|
-
DRIVER_UNEXPECTED_FAILURE
|
|
463
|
+
readonly DRIVER_UNEXPECTED_FAILURE: "DRIVER_UNEXPECTED_FAILURE";
|
|
459
464
|
/**
|
|
460
465
|
* ** Only relevant on k8s dataplanes (i.e. clusters launched with CMv2 - not CMv1).
|
|
461
466
|
* Unexpected new driver pod created
|
|
462
467
|
*/
|
|
463
|
-
UNEXPECTED_POD_RECREATION
|
|
468
|
+
readonly UNEXPECTED_POD_RECREATION: "UNEXPECTED_POD_RECREATION";
|
|
464
469
|
/** Failure due to disabled or inaccessible CMK. */
|
|
465
|
-
GCP_INACCESSIBLE_KMS_KEY_FAILURE
|
|
470
|
+
readonly GCP_INACCESSIBLE_KMS_KEY_FAILURE: "GCP_INACCESSIBLE_KMS_KEY_FAILURE";
|
|
466
471
|
/** Failure due to missing/incorrect permission setup on CMK. */
|
|
467
|
-
GCP_KMS_KEY_PERMISSION_DENIED
|
|
472
|
+
readonly GCP_KMS_KEY_PERMISSION_DENIED: "GCP_KMS_KEY_PERMISSION_DENIED";
|
|
468
473
|
/** Driver pod evicted in Nephos */
|
|
469
|
-
DRIVER_EVICTION
|
|
474
|
+
readonly DRIVER_EVICTION: "DRIVER_EVICTION";
|
|
470
475
|
/** User request for termination directly to cloud */
|
|
471
|
-
USER_INITIATED_VM_TERMINATION
|
|
476
|
+
readonly USER_INITIATED_VM_TERMINATION: "USER_INITIATED_VM_TERMINATION";
|
|
472
477
|
/** GCP Specific IAM API timeout issues during Workload Idenitity (Cluster Identity) binding process */
|
|
473
|
-
GCP_IAM_TIMEOUT
|
|
478
|
+
readonly GCP_IAM_TIMEOUT: "GCP_IAM_TIMEOUT";
|
|
474
479
|
/** Could not find enough AWS resources to fulfill the request */
|
|
475
|
-
AWS_RESOURCE_QUOTA_EXCEEDED
|
|
480
|
+
readonly AWS_RESOURCE_QUOTA_EXCEEDED: "AWS_RESOURCE_QUOTA_EXCEEDED";
|
|
476
481
|
/** Cloud account setup has some error (e.g. pending email verification, blocked) */
|
|
477
|
-
CLOUD_ACCOUNT_SETUP_FAILURE
|
|
482
|
+
readonly CLOUD_ACCOUNT_SETUP_FAILURE: "CLOUD_ACCOUNT_SETUP_FAILURE";
|
|
478
483
|
/** The specified key pair name does not exist. */
|
|
479
|
-
AWS_INVALID_KEY_PAIR
|
|
484
|
+
readonly AWS_INVALID_KEY_PAIR: "AWS_INVALID_KEY_PAIR";
|
|
480
485
|
/** Driver pod creation failure in nephos */
|
|
481
|
-
DRIVER_POD_CREATION_FAILURE
|
|
486
|
+
readonly DRIVER_POD_CREATION_FAILURE: "DRIVER_POD_CREATION_FAILURE";
|
|
482
487
|
/** Cluster terminated manually by on-call due to emergency maintenance */
|
|
483
|
-
MAINTENANCE_MODE
|
|
488
|
+
readonly MAINTENANCE_MODE: "MAINTENANCE_MODE";
|
|
484
489
|
/** Nephos internal error due to insufficient provisioned k8s capacity or insufficient cloud quota */
|
|
485
|
-
INTERNAL_CAPACITY_FAILURE
|
|
490
|
+
readonly INTERNAL_CAPACITY_FAILURE: "INTERNAL_CAPACITY_FAILURE";
|
|
486
491
|
/** Nephos: could not acquire executor pods from pod pool */
|
|
487
|
-
EXECUTOR_POD_UNSCHEDULED
|
|
492
|
+
readonly EXECUTOR_POD_UNSCHEDULED: "EXECUTOR_POD_UNSCHEDULED";
|
|
488
493
|
/** Artifact download failed because it was too slow */
|
|
489
|
-
STORAGE_DOWNLOAD_FAILURE_SLOW
|
|
494
|
+
readonly STORAGE_DOWNLOAD_FAILURE_SLOW: "STORAGE_DOWNLOAD_FAILURE_SLOW";
|
|
490
495
|
/** Artifact download failed because it was throttled by the download server */
|
|
491
|
-
STORAGE_DOWNLOAD_FAILURE_THROTTLED
|
|
496
|
+
readonly STORAGE_DOWNLOAD_FAILURE_THROTTLED: "STORAGE_DOWNLOAD_FAILURE_THROTTLED";
|
|
492
497
|
/** The cluster was terminated because the size of the dynamic spark conf exceeded the limit. */
|
|
493
|
-
DYNAMIC_SPARK_CONF_SIZE_EXCEEDED
|
|
498
|
+
readonly DYNAMIC_SPARK_CONF_SIZE_EXCEEDED: "DYNAMIC_SPARK_CONF_SIZE_EXCEEDED";
|
|
494
499
|
/** Failure to update the instance profile for the cluster. */
|
|
495
|
-
AWS_INSTANCE_PROFILE_UPDATE_FAILURE
|
|
500
|
+
readonly AWS_INSTANCE_PROFILE_UPDATE_FAILURE: "AWS_INSTANCE_PROFILE_UPDATE_FAILURE";
|
|
496
501
|
/** The instance pool did not exist when the cluster was launched. */
|
|
497
|
-
INSTANCE_POOL_NOT_FOUND
|
|
502
|
+
readonly INSTANCE_POOL_NOT_FOUND: "INSTANCE_POOL_NOT_FOUND";
|
|
498
503
|
/** Attempting to launch more instances was rejected as it would exceed the pool's max capacity. */
|
|
499
|
-
INSTANCE_POOL_MAX_CAPACITY_REACHED
|
|
504
|
+
readonly INSTANCE_POOL_MAX_CAPACITY_REACHED: "INSTANCE_POOL_MAX_CAPACITY_REACHED";
|
|
500
505
|
/** The KMS key provided is in an incorrect state. */
|
|
501
|
-
AWS_INVALID_KMS_KEY_STATE
|
|
506
|
+
readonly AWS_INVALID_KMS_KEY_STATE: "AWS_INVALID_KMS_KEY_STATE";
|
|
502
507
|
/** Insufficient capacity failure from GCE API. */
|
|
503
|
-
GCP_INSUFFICIENT_CAPACITY
|
|
508
|
+
readonly GCP_INSUFFICIENT_CAPACITY: "GCP_INSUFFICIENT_CAPACITY";
|
|
504
509
|
/** Rate quota exceeded for GCP API (e.g. Read requests per minute per region). */
|
|
505
|
-
GCP_API_RATE_QUOTA_EXCEEDED
|
|
510
|
+
readonly GCP_API_RATE_QUOTA_EXCEEDED: "GCP_API_RATE_QUOTA_EXCEEDED";
|
|
506
511
|
/** Resource quota exceeded (e.g. # of n1 vCPUs in a region). */
|
|
507
|
-
GCP_RESOURCE_QUOTA_EXCEEDED
|
|
512
|
+
readonly GCP_RESOURCE_QUOTA_EXCEEDED: "GCP_RESOURCE_QUOTA_EXCEEDED";
|
|
508
513
|
/** Subnet IP space exhausted. */
|
|
509
|
-
GCP_IP_SPACE_EXHAUSTED
|
|
514
|
+
readonly GCP_IP_SPACE_EXHAUSTED: "GCP_IP_SPACE_EXHAUSTED";
|
|
510
515
|
/** Missing permissions to launch VM with service account. */
|
|
511
|
-
GCP_SERVICE_ACCOUNT_ACCESS_DENIED
|
|
516
|
+
readonly GCP_SERVICE_ACCOUNT_ACCESS_DENIED: "GCP_SERVICE_ACCOUNT_ACCESS_DENIED";
|
|
512
517
|
/** VM attempting to launch with non-existent service account. */
|
|
513
|
-
GCP_SERVICE_ACCOUNT_NOT_FOUND
|
|
518
|
+
readonly GCP_SERVICE_ACCOUNT_NOT_FOUND: "GCP_SERVICE_ACCOUNT_NOT_FOUND";
|
|
514
519
|
/** Forbidden (403) returned by GCP API. */
|
|
515
|
-
GCP_FORBIDDEN
|
|
520
|
+
readonly GCP_FORBIDDEN: "GCP_FORBIDDEN";
|
|
516
521
|
/** Not found (404) returned by GCP API. */
|
|
517
|
-
GCP_NOT_FOUND
|
|
522
|
+
readonly GCP_NOT_FOUND: "GCP_NOT_FOUND";
|
|
518
523
|
/** Gatekeeper indicated the cluster should be shutdown */
|
|
519
|
-
RESOURCE_USAGE_BLOCKED
|
|
524
|
+
readonly RESOURCE_USAGE_BLOCKED: "RESOURCE_USAGE_BLOCKED";
|
|
520
525
|
/** The data access config of the workspace has changed, and clusters using outdated config will be terminated. */
|
|
521
|
-
DATA_ACCESS_CONFIG_CHANGED
|
|
526
|
+
readonly DATA_ACCESS_CONFIG_CHANGED: "DATA_ACCESS_CONFIG_CHANGED";
|
|
522
527
|
/** Failed to fetch internal PAT token required for init script installation from WSFS/UC volumes */
|
|
523
|
-
ACCESS_TOKEN_FAILURE
|
|
528
|
+
readonly ACCESS_TOKEN_FAILURE: "ACCESS_TOKEN_FAILURE";
|
|
524
529
|
/**
|
|
525
530
|
* It indicates there is a placement v2 protocol rollout/rollback event for the corresponding workspace when
|
|
526
531
|
* processing the placement session on the instance-manager side. A retry will fix the issue by switching back
|
|
527
532
|
* to the correct placement protocol.
|
|
528
533
|
*/
|
|
529
|
-
INVALID_INSTANCE_PLACEMENT_PROTOCOL
|
|
534
|
+
readonly INVALID_INSTANCE_PLACEMENT_PROTOCOL: "INVALID_INSTANCE_PLACEMENT_PROTOCOL";
|
|
530
535
|
/** The cluster was terminated as it failed to resolve budget policy. */
|
|
531
|
-
BUDGET_POLICY_RESOLUTION_FAILURE
|
|
536
|
+
readonly BUDGET_POLICY_RESOLUTION_FAILURE: "BUDGET_POLICY_RESOLUTION_FAILURE";
|
|
532
537
|
/**
|
|
533
538
|
* This customer/error combination is a known issue and is intentionally excluded from termination
|
|
534
539
|
* metrics
|
|
535
540
|
*/
|
|
536
|
-
IN_PENALTY_BOX
|
|
541
|
+
readonly IN_PENALTY_BOX: "IN_PENALTY_BOX";
|
|
537
542
|
/**
|
|
538
543
|
* The cluster was terminated when the primary workspace failed over to the secondary workspace.
|
|
539
544
|
* This is expected because there is no data plane in the secondary workspace.
|
|
540
545
|
*/
|
|
541
|
-
DISASTER_RECOVERY_REPLICATION
|
|
546
|
+
readonly DISASTER_RECOVERY_REPLICATION: "DISASTER_RECOVERY_REPLICATION";
|
|
542
547
|
/** A bootstrap timeout that was caused by misconfiguration on the customer's side */
|
|
543
|
-
BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG
|
|
548
|
+
readonly BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG: "BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG";
|
|
544
549
|
/** Instance unreachable, but due to misconfiguration on the customer's side */
|
|
545
|
-
INSTANCE_UNREACHABLE_DUE_TO_MISCONFIG
|
|
550
|
+
readonly INSTANCE_UNREACHABLE_DUE_TO_MISCONFIG: "INSTANCE_UNREACHABLE_DUE_TO_MISCONFIG";
|
|
546
551
|
/** Bootstrap timeout due to script download failure, but due to misconfiguration on the customer's side */
|
|
547
|
-
STORAGE_DOWNLOAD_FAILURE_DUE_TO_MISCONFIG
|
|
552
|
+
readonly STORAGE_DOWNLOAD_FAILURE_DUE_TO_MISCONFIG: "STORAGE_DOWNLOAD_FAILURE_DUE_TO_MISCONFIG";
|
|
548
553
|
/** CPRF, but due to misconfiguration on the customer's side */
|
|
549
|
-
CONTROL_PLANE_REQUEST_FAILURE_DUE_TO_MISCONFIG
|
|
554
|
+
readonly CONTROL_PLANE_REQUEST_FAILURE_DUE_TO_MISCONFIG: "CONTROL_PLANE_REQUEST_FAILURE_DUE_TO_MISCONFIG";
|
|
550
555
|
/** CPLF, but due to misconfiguration on the customer's side */
|
|
551
|
-
CLOUD_PROVIDER_LAUNCH_FAILURE_DUE_TO_MISCONFIG
|
|
556
|
+
readonly CLOUD_PROVIDER_LAUNCH_FAILURE_DUE_TO_MISCONFIG: "CLOUD_PROVIDER_LAUNCH_FAILURE_DUE_TO_MISCONFIG";
|
|
552
557
|
/** GCP subnet is in transient "resourceNotReady" state. */
|
|
553
|
-
GCP_SUBNET_NOT_READY
|
|
558
|
+
readonly GCP_SUBNET_NOT_READY: "GCP_SUBNET_NOT_READY";
|
|
554
559
|
/** The operation on the cloud provider was cancelled. Possibly due to a user action. */
|
|
555
|
-
CLOUD_OPERATION_CANCELLED
|
|
560
|
+
readonly CLOUD_OPERATION_CANCELLED: "CLOUD_OPERATION_CANCELLED";
|
|
556
561
|
/**
|
|
557
562
|
* If cloud provider indicates instance creation was a success, yet the instance is never created.
|
|
558
563
|
* This can happen in certain edge cases like quota exhaustion on GCP. We have an open bug here:
|
|
559
564
|
* https://partnerissuetracker.corp.google.com/issues/339061883
|
|
560
565
|
*/
|
|
561
|
-
CLOUD_PROVIDER_INSTANCE_NOT_LAUNCHED
|
|
566
|
+
readonly CLOUD_PROVIDER_INSTANCE_NOT_LAUNCHED: "CLOUD_PROVIDER_INSTANCE_NOT_LAUNCHED";
|
|
562
567
|
/** GCP Databricks VM Machine Image is blocked by customer organization policy. */
|
|
563
|
-
GCP_TRUSTED_IMAGE_PROJECTS_VIOLATED
|
|
568
|
+
readonly GCP_TRUSTED_IMAGE_PROJECTS_VIOLATED: "GCP_TRUSTED_IMAGE_PROJECTS_VIOLATED";
|
|
564
569
|
/** cluster terminate can happened when a budget policy limit enforcement activated */
|
|
565
|
-
BUDGET_POLICY_LIMIT_ENFORCEMENT_ACTIVATED
|
|
566
|
-
EOS_SPARK_IMAGE
|
|
570
|
+
readonly BUDGET_POLICY_LIMIT_ENFORCEMENT_ACTIVATED: "BUDGET_POLICY_LIMIT_ENFORCEMENT_ACTIVATED";
|
|
571
|
+
readonly EOS_SPARK_IMAGE: "EOS_SPARK_IMAGE";
|
|
567
572
|
/** Serverless only. There are no eligible K8s for the cluster. */
|
|
568
|
-
NO_MATCHED_K8S
|
|
573
|
+
readonly NO_MATCHED_K8S: "NO_MATCHED_K8S";
|
|
569
574
|
/** Lazy allocation timeout. Timeout before any internal DBR clusters were allocated. */
|
|
570
|
-
LAZY_ALLOCATION_TIMEOUT
|
|
575
|
+
readonly LAZY_ALLOCATION_TIMEOUT: "LAZY_ALLOCATION_TIMEOUT";
|
|
571
576
|
/** CMv2 unable to contact chauffeur or node-daemon on the driver node. */
|
|
572
|
-
DRIVER_NODE_UNREACHABLE
|
|
577
|
+
readonly DRIVER_NODE_UNREACHABLE: "DRIVER_NODE_UNREACHABLE";
|
|
573
578
|
/** Dynamic secret generation failed. */
|
|
574
|
-
SECRET_CREATION_FAILURE
|
|
579
|
+
readonly SECRET_CREATION_FAILURE: "SECRET_CREATION_FAILURE";
|
|
575
580
|
/** Driver or executor pod failed to be scheduled. */
|
|
576
|
-
POD_SCHEDULING_FAILURE
|
|
581
|
+
readonly POD_SCHEDULING_FAILURE: "POD_SCHEDULING_FAILURE";
|
|
577
582
|
/** Driver or executor pod failed to finish assigning. */
|
|
578
|
-
POD_ASSIGNMENT_FAILURE
|
|
583
|
+
readonly POD_ASSIGNMENT_FAILURE: "POD_ASSIGNMENT_FAILURE";
|
|
579
584
|
/** Lazy allocation timeout with unknown reason. */
|
|
580
|
-
ALLOCATION_TIMEOUT
|
|
585
|
+
readonly ALLOCATION_TIMEOUT: "ALLOCATION_TIMEOUT";
|
|
581
586
|
/** Lazy allocation timeout. Maps to NoUnallocatedDbrCluster. */
|
|
582
|
-
ALLOCATION_TIMEOUT_NO_UNALLOCATED_CLUSTERS
|
|
587
|
+
readonly ALLOCATION_TIMEOUT_NO_UNALLOCATED_CLUSTERS: "ALLOCATION_TIMEOUT_NO_UNALLOCATED_CLUSTERS";
|
|
583
588
|
/** Lazy allocation timeout. Maps to NoMatchedUnallocatedDbrCluster. */
|
|
584
|
-
ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS
|
|
589
|
+
readonly ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS: "ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS";
|
|
585
590
|
/** Lazy allocation timeout. Maps to NoUnallocatedReadyDbrCluster. */
|
|
586
|
-
ALLOCATION_TIMEOUT_NO_READY_CLUSTERS
|
|
591
|
+
readonly ALLOCATION_TIMEOUT_NO_READY_CLUSTERS: "ALLOCATION_TIMEOUT_NO_READY_CLUSTERS";
|
|
587
592
|
/** Lazy allocation timeout. Maps to NoMatchedUnallocatedWarmedUpDbrCluster. */
|
|
588
|
-
ALLOCATION_TIMEOUT_NO_WARMED_UP_CLUSTERS
|
|
593
|
+
readonly ALLOCATION_TIMEOUT_NO_WARMED_UP_CLUSTERS: "ALLOCATION_TIMEOUT_NO_WARMED_UP_CLUSTERS";
|
|
589
594
|
/** Lazy allocation timeout. Maps to NoCandidatesWithNodeDaemonK8sReady. */
|
|
590
|
-
ALLOCATION_TIMEOUT_NODE_DAEMON_NOT_READY
|
|
595
|
+
readonly ALLOCATION_TIMEOUT_NODE_DAEMON_NOT_READY: "ALLOCATION_TIMEOUT_NODE_DAEMON_NOT_READY";
|
|
591
596
|
/** Lazy allocation timeout. Maps to NoCandidatesHealthy. */
|
|
592
|
-
ALLOCATION_TIMEOUT_NO_HEALTHY_CLUSTERS
|
|
597
|
+
readonly ALLOCATION_TIMEOUT_NO_HEALTHY_CLUSTERS: "ALLOCATION_TIMEOUT_NO_HEALTHY_CLUSTERS";
|
|
593
598
|
/**
|
|
594
599
|
* When nephos blocking wait for netvisor setup ready signal, terminated by timeout.
|
|
595
600
|
* This error code only applies to clusters with the attribute should_block_for_network_readiness: true
|
|
596
601
|
*/
|
|
597
|
-
NETVISOR_SETUP_TIMEOUT
|
|
602
|
+
readonly NETVISOR_SETUP_TIMEOUT: "NETVISOR_SETUP_TIMEOUT";
|
|
598
603
|
/** Serverless only. The preselected K8s for the cluster is not eligible. */
|
|
599
|
-
NO_MATCHED_K8S_TESTING_TAG
|
|
604
|
+
readonly NO_MATCHED_K8S_TESTING_TAG: "NO_MATCHED_K8S_TESTING_TAG";
|
|
600
605
|
/** The customer's repeatedly attempting to launch clusters with some configuration that the CSP's not able to provide */
|
|
601
|
-
CLOUD_PROVIDER_RESOURCE_STOCKOUT_DUE_TO_MISCONFIG
|
|
606
|
+
readonly CLOUD_PROVIDER_RESOURCE_STOCKOUT_DUE_TO_MISCONFIG: "CLOUD_PROVIDER_RESOURCE_STOCKOUT_DUE_TO_MISCONFIG";
|
|
602
607
|
/** For the GCP CMv1 Migration, we will terminate all CMv2 based clusters with this failure. */
|
|
603
|
-
GKE_BASED_CLUSTER_TERMINATION
|
|
608
|
+
readonly GKE_BASED_CLUSTER_TERMINATION: "GKE_BASED_CLUSTER_TERMINATION";
|
|
604
609
|
/** Lazy allocation timeout. Maps to NoCandidatesHealthyAndWarmedUp. */
|
|
605
|
-
ALLOCATION_TIMEOUT_NO_HEALTHY_AND_WARMED_UP_CLUSTERS
|
|
610
|
+
readonly ALLOCATION_TIMEOUT_NO_HEALTHY_AND_WARMED_UP_CLUSTERS: "ALLOCATION_TIMEOUT_NO_HEALTHY_AND_WARMED_UP_CLUSTERS";
|
|
606
611
|
/** Docker container's OS was not valid. */
|
|
607
|
-
DOCKER_INVALID_OS_EXCEPTION
|
|
612
|
+
readonly DOCKER_INVALID_OS_EXCEPTION: "DOCKER_INVALID_OS_EXCEPTION";
|
|
608
613
|
/** Something went wrong during the creation of the docker container. */
|
|
609
|
-
DOCKER_CONTAINER_CREATION_EXCEPTION
|
|
614
|
+
readonly DOCKER_CONTAINER_CREATION_EXCEPTION: "DOCKER_CONTAINER_CREATION_EXCEPTION";
|
|
610
615
|
/** Customer passed in a docker image that's too large for the instance. */
|
|
611
|
-
DOCKER_IMAGE_TOO_LARGE_FOR_INSTANCE_EXCEPTION
|
|
616
|
+
readonly DOCKER_IMAGE_TOO_LARGE_FOR_INSTANCE_EXCEPTION: "DOCKER_IMAGE_TOO_LARGE_FOR_INSTANCE_EXCEPTION";
|
|
612
617
|
/** The cluster was terminated because the DNS resolution failed. */
|
|
613
|
-
DNS_RESOLUTION_ERROR
|
|
618
|
+
readonly DNS_RESOLUTION_ERROR: "DNS_RESOLUTION_ERROR";
|
|
614
619
|
/** Org policy is preventing a GCE API operation from being executed. */
|
|
615
|
-
GCP_DENIED_BY_ORG_POLICY
|
|
620
|
+
readonly GCP_DENIED_BY_ORG_POLICY: "GCP_DENIED_BY_ORG_POLICY";
|
|
616
621
|
/** Customer passed in a secret that they do not have permissions to resolve. */
|
|
617
|
-
SECRET_PERMISSION_DENIED
|
|
622
|
+
readonly SECRET_PERMISSION_DENIED: "SECRET_PERMISSION_DENIED";
|
|
618
623
|
/** Start of network health check generated failures */
|
|
619
|
-
NETWORK_CHECK_NIC_FAILURE
|
|
620
|
-
NETWORK_CHECK_DNS_SERVER_FAILURE
|
|
621
|
-
NETWORK_CHECK_STORAGE_FAILURE
|
|
622
|
-
NETWORK_CHECK_METADATA_ENDPOINT_FAILURE
|
|
623
|
-
NETWORK_CHECK_CONTROL_PLANE_FAILURE
|
|
624
|
-
NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE
|
|
624
|
+
readonly NETWORK_CHECK_NIC_FAILURE: "NETWORK_CHECK_NIC_FAILURE";
|
|
625
|
+
readonly NETWORK_CHECK_DNS_SERVER_FAILURE: "NETWORK_CHECK_DNS_SERVER_FAILURE";
|
|
626
|
+
readonly NETWORK_CHECK_STORAGE_FAILURE: "NETWORK_CHECK_STORAGE_FAILURE";
|
|
627
|
+
readonly NETWORK_CHECK_METADATA_ENDPOINT_FAILURE: "NETWORK_CHECK_METADATA_ENDPOINT_FAILURE";
|
|
628
|
+
readonly NETWORK_CHECK_CONTROL_PLANE_FAILURE: "NETWORK_CHECK_CONTROL_PLANE_FAILURE";
|
|
629
|
+
readonly NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE: "NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE";
|
|
625
630
|
/** Driver has been down or unresponsive for an extended period of time */
|
|
626
|
-
DRIVER_UNHEALTHY
|
|
631
|
+
readonly DRIVER_UNHEALTHY: "DRIVER_UNHEALTHY";
|
|
627
632
|
/** cluster request is denied due to disallowed usage policy entitlement */
|
|
628
|
-
USAGE_POLICY_ENTITLEMENT_DENIED
|
|
633
|
+
readonly USAGE_POLICY_ENTITLEMENT_DENIED: "USAGE_POLICY_ENTITLEMENT_DENIED";
|
|
629
634
|
/** Request exceeded MAX_ACTIVE_DBR_PODS_PER_K8S_CLUSTER quota - too many active pods on the K8s cluster */
|
|
630
|
-
K8S_ACTIVE_POD_QUOTA_EXCEEDED
|
|
635
|
+
readonly K8S_ACTIVE_POD_QUOTA_EXCEEDED: "K8S_ACTIVE_POD_QUOTA_EXCEEDED";
|
|
631
636
|
/** Request exceeded MAX_PODS_PER_CLOUD_ACCOUNT quota - subscription/cloud account pod limit reached */
|
|
632
|
-
CLOUD_ACCOUNT_POD_QUOTA_EXCEEDED
|
|
637
|
+
readonly CLOUD_ACCOUNT_POD_QUOTA_EXCEEDED: "CLOUD_ACCOUNT_POD_QUOTA_EXCEEDED";
|
|
633
638
|
/** Start of network health check generated failures due to misconfiguration */
|
|
634
|
-
NETWORK_CHECK_NIC_FAILURE_DUE_TO_MISCONFIG
|
|
635
|
-
NETWORK_CHECK_DNS_SERVER_FAILURE_DUE_TO_MISCONFIG
|
|
636
|
-
NETWORK_CHECK_STORAGE_FAILURE_DUE_TO_MISCONFIG
|
|
637
|
-
NETWORK_CHECK_METADATA_ENDPOINT_FAILURE_DUE_TO_MISCONFIG
|
|
638
|
-
NETWORK_CHECK_CONTROL_PLANE_FAILURE_DUE_TO_MISCONFIG
|
|
639
|
-
NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE_DUE_TO_MISCONFIG
|
|
639
|
+
readonly NETWORK_CHECK_NIC_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_NIC_FAILURE_DUE_TO_MISCONFIG";
|
|
640
|
+
readonly NETWORK_CHECK_DNS_SERVER_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_DNS_SERVER_FAILURE_DUE_TO_MISCONFIG";
|
|
641
|
+
readonly NETWORK_CHECK_STORAGE_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_STORAGE_FAILURE_DUE_TO_MISCONFIG";
|
|
642
|
+
readonly NETWORK_CHECK_METADATA_ENDPOINT_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_METADATA_ENDPOINT_FAILURE_DUE_TO_MISCONFIG";
|
|
643
|
+
readonly NETWORK_CHECK_CONTROL_PLANE_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_CONTROL_PLANE_FAILURE_DUE_TO_MISCONFIG";
|
|
644
|
+
readonly NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE_DUE_TO_MISCONFIG: "NETWORK_CHECK_MULTIPLE_COMPONENTS_FAILURE_DUE_TO_MISCONFIG";
|
|
640
645
|
/**
|
|
641
646
|
* CMv2 could not resolve the DBR image for versionless workloads (REPL, GENERIC).
|
|
642
647
|
* This typically happens when no spark version is found from the channel mapping
|
|
643
648
|
* and the workload is versionless-enabled.
|
|
644
649
|
*/
|
|
645
|
-
DBR_IMAGE_RESOLUTION_FAILURE
|
|
646
|
-
CONTROL_PLANE_CONNECTION_FAILURE
|
|
647
|
-
CONTROL_PLANE_CONNECTION_FAILURE_DUE_TO_MISCONFIG
|
|
648
|
-
RATE_LIMITED
|
|
650
|
+
readonly DBR_IMAGE_RESOLUTION_FAILURE: "DBR_IMAGE_RESOLUTION_FAILURE";
|
|
651
|
+
readonly CONTROL_PLANE_CONNECTION_FAILURE: "CONTROL_PLANE_CONNECTION_FAILURE";
|
|
652
|
+
readonly CONTROL_PLANE_CONNECTION_FAILURE_DUE_TO_MISCONFIG: "CONTROL_PLANE_CONNECTION_FAILURE_DUE_TO_MISCONFIG";
|
|
653
|
+
readonly RATE_LIMITED: "RATE_LIMITED";
|
|
649
654
|
/** The cluster was terminated because mutual TLS port 8443 check failed. */
|
|
650
|
-
MTLS_PORT_CONNECTIVITY_FAILURE
|
|
655
|
+
readonly MTLS_PORT_CONNECTIVITY_FAILURE: "MTLS_PORT_CONNECTIVITY_FAILURE";
|
|
651
656
|
/** The cluster was terminated because hivemetastore connectivity check failed. */
|
|
652
|
-
HIVEMETASTORE_CONNECTIVITY_FAILURE
|
|
653
|
-
}
|
|
657
|
+
readonly HIVEMETASTORE_CONNECTIVITY_FAILURE: "HIVEMETASTORE_CONNECTIVITY_FAILURE";
|
|
658
|
+
};
|
|
659
|
+
export type TerminationCode = (typeof TerminationCode)[keyof typeof TerminationCode] | (string & {});
|
|
654
660
|
/** type of the termination */
|
|
655
|
-
export declare
|
|
661
|
+
export declare const TerminationType: {
|
|
656
662
|
/** Termination succeeded normally */
|
|
657
|
-
SUCCESS
|
|
663
|
+
readonly SUCCESS: "SUCCESS";
|
|
658
664
|
/** Non-retryable. Client must fix parameters before reattempting the cluster creation */
|
|
659
|
-
CLIENT_ERROR
|
|
665
|
+
readonly CLIENT_ERROR: "CLIENT_ERROR";
|
|
660
666
|
/** Databricks service issue. Clients may retry */
|
|
661
|
-
SERVICE_FAULT
|
|
667
|
+
readonly SERVICE_FAULT: "SERVICE_FAULT";
|
|
662
668
|
/** AWS or Azure infrastructure issue. Clients may retry after the underlying cloud issue is resolved */
|
|
663
|
-
CLOUD_FAILURE
|
|
664
|
-
}
|
|
665
|
-
export
|
|
669
|
+
readonly CLOUD_FAILURE: "CLOUD_FAILURE";
|
|
670
|
+
};
|
|
671
|
+
export type TerminationType = (typeof TerminationType)[keyof typeof TerminationType] | (string & {});
|
|
672
|
+
export declare const WarehouseType: {
|
|
666
673
|
/** UNDOCUMENTED. Indicates no value is specified. */
|
|
667
|
-
TYPE_UNSPECIFIED
|
|
674
|
+
readonly TYPE_UNSPECIFIED: "TYPE_UNSPECIFIED";
|
|
668
675
|
/** Classic warehouse type */
|
|
669
|
-
CLASSIC
|
|
676
|
+
readonly CLASSIC: "CLASSIC";
|
|
670
677
|
/** Pro warehouse type */
|
|
671
|
-
PRO
|
|
672
|
-
}
|
|
673
|
-
export
|
|
678
|
+
readonly PRO: "PRO";
|
|
679
|
+
};
|
|
680
|
+
export type WarehouseType = (typeof WarehouseType)[keyof typeof WarehouseType] | (string & {});
|
|
681
|
+
export declare const EndpointHealth_Status: {
|
|
674
682
|
/** UNDOCUMENTED. Indicates no value is specified. An implementation detail. */
|
|
675
|
-
STATUS_UNSPECIFIED
|
|
683
|
+
readonly STATUS_UNSPECIFIED: "STATUS_UNSPECIFIED";
|
|
676
684
|
/** Endpoint is functioning normally and there are no known issues. */
|
|
677
|
-
HEALTHY
|
|
685
|
+
readonly HEALTHY: "HEALTHY";
|
|
678
686
|
/**
|
|
679
687
|
* Endpoint might be functional, but there are some known issues.
|
|
680
688
|
* Performance might be affected.
|
|
681
689
|
*/
|
|
682
|
-
DEGRADED
|
|
690
|
+
readonly DEGRADED: "DEGRADED";
|
|
683
691
|
/** Endpoint is severely affected. Likely will not be able to serve queries. */
|
|
684
|
-
FAILED
|
|
685
|
-
}
|
|
692
|
+
readonly FAILED: "FAILED";
|
|
693
|
+
};
|
|
694
|
+
export type EndpointHealth_Status = (typeof EndpointHealth_Status)[keyof typeof EndpointHealth_Status] | (string & {});
|
|
686
695
|
/** Configures the channel name and DBSQL version of the warehouse. CHANNEL_NAME_CUSTOM should be chosen only when `dbsql_version` is specified. */
|
|
687
696
|
export interface Channel {
|
|
688
697
|
name?: ChannelName | undefined;
|