What Should I Do If Error Message "Read timedout" Is Displayed During DWS Data Migration?
Symptom
When CDM is used to migrate data from a DWS cluster to another, the following error is reported after some data is written:
org.postgresql.util.PSQLException: Database connection failed when ending copy…….caused by: java.net.SocketTimeoutExcepetion:Read timed out;
Fault Analysis
In both the source and destination job configurations, the where clause rather than an index column is used to filter data. The query scans the entire table that contains hundreds of millions of rows. As a result, the JDBC database connection fails and data reading times out, causing a sqoop exception and job failure.
In a migration job, CDM functions as a client to extract some data from the source and write the data to the destination. Then, CDM repeats this process until all data is written to the destination. You can add advanced attribute socketTimeout and set an interval between each data extraction and writing process so that the CDM session is always normal.
Solution
Increase the JDBC connection timeout interval and run the migration job again.
- Go to the Links page and locate the connector between the source and destination.
- Click Edit in the Operation column. On the displayed page, click Show Advanced Attributes and then Add to add attribute socketTimeout and set its value to 36000. Then test and save the link.
- Restart the job and wait until it is successfully executed.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot