Cloud Data Streaming Service troubleshooting

Available in Classic and VPC

You might run into the following problems when using Cloud Data Streaming Service. Find out causes and possible solutions.

403 Forbidden error

A 403 Forbidden error occurs when you attempt to access the management tool provided by the manager node using IP:Port.

Cause

Cloud Data Streaming Service now supports Single Sign-On (SSO) authentication for Kafka-UI. If you access directly using IP:Port, the authentication process (OAUTH) cannot be handled, which may result in a 403 Forbidden error and other errors.

Solution

To access the service properly, you must use the official access domain (URL) with SSO authentication applied, regardless of the subnet type.

• If you are a main account user, log in using the account used for the NAVER Cloud Platform portal.
• If you are a sub account user, select Sub Account Login on the login interface and log in using the authorized sub account credentials.

Login error

An error occurs during login.

Cause

In some browser environments, the login process may not function properly due to browser redirection errors.

Solution

The solutions are:

1. Log out of the NAVER Cloud Platform portal and console, and then close the browser.
2. Open a new browser window and clear the browser cache.
3. Log in again.

Disk usage risk

You received an email indicating that a broker node was stopped due to disk usage risk.

Cause

If the disk usage of a broker node remains at 95% or higher, an email is sent before a disk full failure occurs. If disk usage reaches 100% and the broker node stops, recovery through Kafka-UI is difficult, so immediate action is required.

Solution

Change the data retention period of the topic in Kafka-UI (a reduction to 1/2 of the current value is recommended), and then restart the broker node in the console. When the broker node restarts, data that has exceeded the retention period is deleted, allowing normal operation.
If disk usage reaches 100% and the broker node stops, recovery through Kafka-UI is difficult, please contact Customer Support.

Log collection issue

Cluster logs are not collected.

Cause

Clusters created before November 25, 2021 do not collect logs.

Solution

For log collection, please contact Customer Support.

Cluster status error

The cluster does not appear to be operating normally.

Cause

One of the main causes of issues during cluster operation is a disk full condition.

Solution

• Click [View cluster status] in the cluster list to check the cluster status.
• If there is an issue with the Zookeeper or Kafka process, click Cluster restart > Restart all services to restart the cluster. If the issue is not resolved after restarting, contact Customer Support.
• To manage disk usage, configure events for disk usage using the Monitoring menu in Cloud Data Streaming Service or the Cloud Insight service. For information on how to configure events using Cloud Insight, refer to Monitoring Cloud Data Streaming Service with Cloud Insight.

Cluster creation delay

The server status does not change after creating the cluster.

Cause

Cluster creation may fail if the communication required for creation is blocked.

Solution

Create a new cluster without removing the separately added NACL or blocking the default ACG.

Redirected to the login interface when accessing the management tool

When accessing the management tool, you are redirected to the NAVER Cloud Platform login interface.

Cause

The management tool login method has been changed to SSO login using the NAVER Cloud Platform account.

Solution

On the login interface displayed when accessing the management tool, enter the account credentials used for the NAVER Cloud Platform portal and log in again.

Learning resources

We offer various materials for you to explore. To learn more about Cloud Data Streaming Service, check out these helpful links:

• FAQs: Cloud Data Streaming Service FAQs
• API guide: Cloud Data Streaming Service API guide
• NAVER Cloud Platform's blog: Create Search Engine Service and Cloud Data Streaming Service using Terraform!
• NAVER Cloud Platform's blog: Log collection and storage using Cloud Data Streaming Service and Elasticsearch Service