Cluster Errors
CL00
Error Message:
Invalid or missing cluster name/ID. Please provide a valid cluster name/ID
Description:
During operations (such as edit, suspend, resume, delete) on a cluster via API, users encounter an error when the provided cluster name/ID is incorrect or missing. This prevents the system from identifying the target cluster for the requested operation.
Solution:
To resolve this error, users should verify and provide the correct cluster name/ID when performing operations on a cluster through the API. Double-checking the provided cluster name/ID will help avoid this issue and ensure that the operation is executed on the intended cluster.
Error Type
Programmatic
CL01
Error Message:
Cluster creation failed: Name already exists.
Description:
When attempting to create a cluster through the API, the provided name for the cluster matches an existing cluster's name in the system. Each cluster must have a unique name to ensure proper identification and management within the workspace.
Solution:
To resolve this issue, the user should provide a unique name for the cluster that does not already exist within the workspace. Choose a different name that accurately reflects the purpose or characteristics of the cluster being created. This will ensure successful creation of the cluster without conflicts.
Error Type
Programmatic
CL02
Error Message:
Invalid cluster size value provided.
Description:
During the creation of a cluster, an invalid size value was provided. The allowed range for the cluster size is between XS to XXXL, or CUSTOM for a custom size. Providing an input outside of this range will result in an error.
Solution:
To resolve this issue, ensure that the cluster size value provided falls within the allowed range of XS to XXXL, or CUSTOM for a custom size. Review the input parameters and correct the cluster size value accordingly before attempting to create the cluster again.
Error Type
Programmatic
CL03
Error Message:
Catalog name/ID not provided or incorrect.
Description:
During the creation or editing of a cluster, a valid catalog name/ID was not provided, or an incorrect catalog name/ID was supplied. The catalog is essential for obtaining the customer's metadata information necessary for cluster operation.
Solution:
To resolve this issue, ensure that a valid and correct catalog name/ID is provided when creating or editing the cluster. Double-check the input parameters and verify that the catalog name/ID corresponds to the appropriate catalog within the workspace. Provide the correct catalog name/ID to proceed with the operation successfully.
Error Type
Programmatic
CL04
Error Message:
Workspace name/ID not provided or incorrect.
Description:
During the creation or editing of a cluster, the provided workspace name or ID is either missing or incorrect. The workspace serves as a high-level layer under which clusters are created, and it's essential for organizing and managing resources effectively.
Solution:
To resolve this issue, ensure that the correct workspace name or ID is provided when creating or editing the cluster. Double-check the input parameters and verify that the workspace name or ID corresponds to an existing workspace within the workspace. Provide the correct workspace information to proceed with the operation successfully.
Error Type
Programmatic
CL12
Error Message:
Insufficient compute resources available in your cloud account.
Description:
During cluster creation, editing, or resuming, the system checks for the availability of compute resources in the cloud. If there are insufficient resources available in the cloud account or if the specified EC2 instance with the required compute cores is not available, this error occurs. Compute resources are essential for query planning and execution within the cluster.
Solution:
To resolve this issue, check the cloud account for available compute resources and ensure that there are enough resources to create or resume the cluster. Additionally, verify that the specified EC2 instance with the required compute cores is available and accessible. If resources are insufficient, consider allocating more resources to the cloud account or selecting a different instance type with the required specifications.
CL13
Error Message:
Delete operation already in progress for this cluster.
Description:
When attempting to perform a delete operation on a cluster, an error occurs if the same operation is already in progress for the same cluster. This prevents simultaneous delete operations on the cluster, ensuring data consistency and preventing potential conflicts.
Solution:
To resolve this issue, the user should wait until the ongoing delete operation on the cluster is completed.
CL28
Error Message:
An unexpected error occurred while creating the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL29
Error Message:
An unexpected error occurred while resuming the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL36
Error Message:
An unexpected error occurred while suspending the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL37
Error Message:
An unexpected error occurred while editing the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL38
Error Message:
An unexpected error occurred while performing the operation on the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL41
Error Message:
An unexpected error occurred while performing the operation on the cluster.
Description:
During the execution of an operation on the cluster, an unexpected error has occurred in the backend. Users are advised to contact help@e6data.com to report the issue and get assistance from the technical team in resolving it.
Solution:
To address this issue, user can retry the same operation after a few minutes. In case the issue still persists please reach out to us on help@e6data.com for further investigation and resolution of the problem. Our, support team will analyze the error details, troubleshoot the issue, and provide a comprehensive information.
CL49
Error Message:
Cluster is already suspended.
Description:
When attempting to suspend a cluster through the API, a warning occurs if the cluster is already in a suspended state.
Solution:
To address this issue, the user should verify the status of the cluster before attempting to suspend it through the API. If the cluster is already suspended, no further action is necessary. If the user needs to resume operations on the cluster, they should first check its status and then proceed accordingly.
Error Type
Programmatic
CL51
Error Message:
Cluster action failed due to insufficient compute resources.
Description:
When attempting to perform an action on a cluster, such as creation, deletion, or modification, the operation fails because there are insufficient compute resources available in the Availability Zone of the user's cloud account. This error could also occur if the specified EC2 instance with the required compute cores is not available.
Solution:
To resolve this issue, the user should check the resource availability in the Availability Zone where the cluster is being deployed. If resources are insufficient, consider allocating more resources. Additionally, ensure that the specified EC2 instance type with the required compute cores is available in the selected region. Adjusting resource allocations and selecting appropriate instance types will enable successful cluster operations without encountering compute resource limitations.
CL57
Error Message:
Cluster action failed due to insufficient permissions .
Description:
The attempted action on the cluster failed because the user's cloud account lacks the necessary permissions. Without the required permissions, it cannot execute the requested operation successfully. As a result, all changes made during the operation will be rolled back, and the cluster will revert to its previous status.
Solution:
To resolve this issue, the user must ensure that the appropriate permissions are granted in their cloud account to perform the desired cluster operations. This may involve adjusting IAM (Identity and Access Management) policies or granting specific permissions related to the creation, modification, or deletion of clusters. Once the necessary permissions are configured, the user can retry the operation, ensuring successful execution without encountering permission-related errors.
CL60
Error Message:
Cannot attach endpoint while cluster is in a failed state or undergoing a process.
Description:
When attempting to attach an endpoint to the cluster, an error occurs if the cluster is in a failed state or is currently undergoing a process. Endpoints allow external access to the cluster, and attaching them requires the cluster to be in a stable state. If the cluster is failed, or if it's undergoing another process, attaching an endpoint is not possible.
Solution:
To resolve this issue, the user should wait until the cluster finishes its ongoing process and is in a stable state. If the cluster is in a failed state, the user should consider using a different cluster instead. Once the cluster is stable and operational, the user can proceed to attach the endpoint successfully. This ensures that endpoints are only attached to clusters that are functioning properly, maintaining the integrity and reliability of external access to the SQL engine.
Error Type
Programmatic
CL62
Error Message:
Cluster is already active.
Description:
When attempting to resume a cluster through the API, an error occurs if the cluster is already in an active state.
Solution:
To resolve this issue, the user should verify the status of the cluster before attempting to resume it through the API. If the cluster is already active, no further action is necessary. The user can continue using the cluster for query execution.
Error Type
Programmatic
CL63
Error Message:
The requested cluster action encountered an error while attempting to pull an image from the e6data repository.
Description:
During operations such as create, edit, or resume on a cluster, an error occurs when the process attempts to pull an image of a cluster component from the e6data repository.
Solution:
To resolve this issue, the user should contact customer help@e6data.com for assistance. Support team can investigate the cause of the failure to pull the image from the repository and provide guidance on resolving the issue.
CL64
Error Message:
Cluster operation failed due to infrastructure unavailability.
Description:
During operations such as resume, edit, or create on a cluster, the process fails because the required infrastructure is unavailable. This could occur due to maintenance, network issues, or other unforeseen circumstances that affect the availability of the underlying infrastructure required for cluster operations.
Solution:
To address this issue, the user has two options. Firstly, they can contact help@e6data.com to report the issue and seek assistance in resolving it. Support team can investigate the cause of the infrastructure unavailability and provide guidance on how to proceed. Alternatively, the user can wait for some time until the infrastructure is back online. The infrastructure may become available again after a period of downtime or maintenance.
CL65
Error Message:
Insufficient Cluster Size for Target QPS (Queries Per Second). The existing cluster size falls short of accommodating the desired QPS. We advise increasing the cluster size to a () minimum of the recommended executors or more for the desired QPS. Adjustments to the cluster size are recommended to ensure optimal performance.
Description:
This error occurs when the existing cluster size is insufficient to handle the desired Queries Per Second (QPS) rate. The cluster lacks the necessary computational resources to process queries at the desired speed effectively.
Solution:
To resolve this issue and ensure optimal performance, it is recommended to increase the cluster size to a minimum of the recommended number of executors or more to accommodate the desired QPS. By adjusting the cluster size, you can allocate additional computational resources, enabling the cluster to handle the workload more efficiently and meet the desired QPS target. Be sure to monitor performance after making adjustments to ensure that the cluster can adequately handle the workload without encountering further resource limitations.
CL66
Error Message:
Cluster name cannot be the same as the workspace name.
Description:
When attempting to create a cluster, an error occurs if the specified cluster name is the same as the workspace name. Each cluster must have a unique name for proper identification and management. Naming conflicts between the cluster and workspace can lead to confusion and potential errors in operations.
Solution:
To resolve this issue, the user should choose a different name for the cluster that is distinct from the workspace name. Selecting a unique name for the cluster ensures clear identification and prevents naming conflicts within the workspace. After choosing a suitable cluster name, retry the cluster creation process with the new name to proceed successfully.
Error Type
Programmatic
CL67
Error Message:
Failed to delete cluster due to attached endpoints.
Description:
During the deletion of a cluster, an error occurs because the endpoints attached to the cluster fail to detach. This failure could be due to delays in the deletion of backend resources associated with the endpoints.
Solution:
To resolve this issue, the user should manually detach the cluster from the attached endpoints. Navigate to the connectivity section of the platform and access the endpoints page. From there, locate the attached endpoints associated with the cluster and initiate the detachment process manually. Once the cluster is detached from all endpoints, retry the deletion process, and it should proceed successfully without encountering any errors. This manual intervention ensures that the cluster can be deleted properly, even if there are delays in the detachment of endpoints.
CL68
Error Message:
Cluster operations failed: Required Kubernetes pods are inactive.
Description:
The attempted cluster operation has failed because the necessary Kubernetes pods required for its functioning are inactive. This could be due to either insufficient resources or the deletion of the pods.
Solution:
To resolve this issue, the user should first check the availability of resources in the cluster's environment. Ensure that there are sufficient resources allocated to the cluster to support the activation of pods. Additionally, verify if the pods were accidentally deleted. If the pods cannot be activated or if they were deleted, it may be necessary to delete the existing cluster and create a new one.
Error Type
Programmatic
CL69
Error Message:
Cannot attach multiple cross-account catalogs to the cluster.
Description:
The user will encounter this error while attempting to attach catalogs to the cluster because currently we support only one cross-account catalog attachment per cluster. Having multiple cross-account catalogs attached to the cluster is not supported, leading to this error.
Solution:
To resolve this issue, ensure that only one cross-account catalog is attached to the cluster.
Last updated