Help Center/ Distributed Cache Service/ User Guide (Paris Region) / FAQs/ Redis Usage/ Why Does It Take a Long Time to Start a Cluster DCS Instance?

Updated on 2022-02-21 GMT+08:00

View PDF

Why Does It Take a Long Time to Start a Cluster DCS Instance?

Possible cause: When a cluster instance is started, status and data are synchronized between the nodes of the instance. If a large amount of data is continuously written into the instance before the synchronization is complete, the synchronization will be prolonged and the instance remains in the Starting state. After the synchronization is complete, the instance enters the Running state.

Solution: Start writing data to an instance only after the instance has been started.

Parent topic: Redis Usage

Previous topic: Does DCS Support Cross-AZ Deployment?

Next topic: Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.