Help Center>
CloudTable Service>
FAQs>
General>
What Should I Do If Concurrent Tasks Run Slowly When Python Accesses CloudTable Through Thrift?
Updated on 2024-04-30 GMT+08:00
What Should I Do If Concurrent Tasks Run Slowly When Python Accesses CloudTable Through Thrift?
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: General
General FAQs
- What Services Does a CloudTable Cluster Provide?
- Why Do I Choose CloudTable Service?
- How Do I Prepare for Creating a CloudTable HBase Cluster?
- What Should I Pay Attention to When Using CloudTable Service?
- What Compression Algorithms Are Supported by CloudTable HBase Clusters?
- Can I Stop CloudTable Service?
- Which Programming Languages Are Supported by HBase External APIs in CloudTable?
- How Do I Determine the Number of Faulty RegionServers?
- What Special Characters Does CloudTable HBase Support?
- What Can I Do If the Index Table Does Not Match the Data Table After CloudTable Data Is Deleted?
- What Should I Do If Concurrent Tasks Run Slowly When Python Accesses CloudTable Through Thrift?
- How do I view the TTL attribute of HBase shell?
- Why Are My Server Resources Released?
- How Do I Delete a Cluster?
- How Do I Stop Services and Release Resources?
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
