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
You connect to the management tool provided by the manager node at IP: Port, but you get a 403 Forbidden error.
Cause
Cloud Data Streaming Service now supports Single Sign-On (SSO) authentication for CMAK and Kafka-UI. If you access it directly through IP: Port, the service cannot process the OAUTH authentication flow, which can result in 403 Forbidden and other errors.
Solution
To connect successfully, you must use the official SSO-enabled access domain or URL, regardless of the subnet type.
- If you are a main account user, login with the account you use for the NAVER Cloud Platform portal.
- If you are a sub account user, on the login page select Login with a sub account, then login with the sub account that has the required permissions.
Login error
Error occurs when you login.
Cause
In some browser environments, a browser redirection error prevents the login flow from working correctly.
Solution
Follow these steps to solve this problem:
- Sign out from the NAVER Cloud Platform portal and the console, then close your browser.
- Open a new browser window, then clear your browser cache.
- Go to the CMAK domain and login again.
Disk usage risk
You received an email stating that a broker node stopped due to Disk usage risk.
Cause
If a broker node’s Disk usage stays at 95% or higher, the system sends an email before a disk full condition occurs. If Disk usage reaches 100% and the broker node stops, recovery through CMAK is difficult and requires urgent action.
Solution
In CMAK, reduce the Topic data retention period (recommended at about half of the current setting) then restart the broker node in the console. After the broker node restarts, data past the retention period is deleted and you can operate normally.
If Disk usage reaches 100% and the broker node stops, recovery through CMAK is difficult, contact Customer Support.
Log collection issues
The cluster logs are not being collected.
Cause
Clusters created before November 25, 2021 do not collect logs.
Solution
If you need log collection, contact Customer Support.
Cluster status error
The cluster does not appear to be operating normally.
Cause
One of the major causes during cluster operations is a Disk full condition.
Solution
- In the cluster list, click the [View cluster status] button to check the cluster status.
- If the ZooKeeper or Kafka process has an issue, go to Restart cluster > Restart all services to restart the cluster. If the issue persists after the restart, contact Customer Support.
- To manage Disk usage, configure events for disk usage from the Monitoring menu in Cloud Data Streaming Service or by using the Cloud Insight service. For how to configure events with Cloud Insight, see Monitor Cloud Data Streaming Service with Cloud Insight.
NAVER Cloud Platform is not responsible for Kafka process failures caused by Disk full conditions.
Cluster creation delay
You created a cluster, but the server status does not change.
Cause
If communication required for cluster creation is blocked, creation can fail.
Solution
Disable any additional NACL or create a new cluster without blocking the default ACG.
Redirected to the login screen when accessing CMAK or Grafana
When you access CMAK or Grafana, you are redirected to the NAVER Cloud Platform portal login screen.
Cause
CMAK and Grafana authentication has changed to SSO login with your NAVER Cloud Platform account.
Solution
When you access CMAK and the login screen appears, enter the account ID and password you use for the NAVER Cloud Platform portal, then 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 blog: Create Search Engine Service and Cloud Data Streaming Service with Terraform!
- NAVER Cloud Platform blog: Log collection and storage with Cloud Data Streaming Service and Elasticsearch Service
If you're still having trouble finding what you need, click on the feedback icon and send us your thoughts and requests. We'll use your feedback to improve this guide.