Help Center>
Data Lake Insight>
FAQs>
Datasource Connections>
Datasource Connection O&M>
RegionTooBusyException Is Reported When Data Is Imported to a CloudTable HBase Table Through a Datasource Table
Updated on 2023-05-19 GMT+08:00
RegionTooBusyException Is Reported When Data Is Imported to a CloudTable HBase Table Through a Datasource Table
Symptom
A datasource table was used to import data to a CloudTable HBase table. This HBase table contains a column family and a rowkey for 100 million simulating data records. The data volume is 9.76 GB. The job failed after 10 million data records were imported.
Cause Analysis
- View driver error logs.
- View executor error logs.
- View task error logs.
The rowkey was poorly designed causing a large amount of traffic redirected to single or very few numbers of nodes.
Procedure
- Pre-partition the HBase.
- Hash the rowkey.
Summary and Suggestions
Distribute data to different RegionServer. Add distribute by rand() to the end of the insert statement.
Parent topic: Datasource Connection O&M
Datasource Connection O&M FAQs
- Why Is the Error Message "communication link failure" Displayed When I Use a Newly Activated Datasource Connection?
- Connection Times Out During MRS HBase Datasource Connection, and No Error Is Recorded in Logs
- Why Can't I Find the Subnet When Creating a DLI Datasource Connection?
- Error Message "Incorrect string value" Is Displayed When insert overwrite Is Executed on a Datasource RDS Table
- Null Pointer Error Is Displayed When the System Creates a Datasource RDS Table
- Error Message "org.postgresql.util.PSQLException: ERROR: tuple concurrently updated" Is Displayed When the System Executes insert overwrite on a Datasource GaussDB(DWS) Table
- RegionTooBusyException Is Reported When Data Is Imported to a CloudTable HBase Table Through a Datasource Table
- A Null Value Is Written Into a Non-Null Field When a DLI Datasource Connection Is Used to Connect to a GaussDB(DWS) Table
- An Insert Operation Failed After the Schema of the GaussDB(DWS) Source Table Is Updated
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
