Help Center/ CloudTable Service/ FAQs/ Connection and Access/ What Should I Do If It Takes a Long Time to Concurrently Access an HBase Cluster Through the Thrift Interface Using Python?

Updated on 2025-08-14 GMT+08:00

View PDF

What Should I Do If It Takes a Long Time to Concurrently Access an HBase Cluster Through the Thrift Interface Using Python?

Symptom

When a CloudTable HBase data table is accessed, concurrent tasks run slowly.

Possible Causes

GC memory leakage occurs on cluster nodes. Perform gray restart on the nodes.

In addition, check whether the load is too high. If the nodes are overloaded, contact related personnel.

Solutions

Contact maintenance personnel to restart the RegionServer instance.

Parent topic: Connection and Access

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.

Chatbot