FDI Task Fails to Be Executed Because DWS Changes to the read-only State
Cause Analysis
When the DWS disk space reaches the threshold, for example, 80%, or data skew occurs in some tables with a large amount of data, the DWS cluster becomes read-only. On the FDI side, all tasks for accessing DWS stopped abnormally at a certain time point.
Solution
Handle the read-only issue of DWS. After the database service is restored, directly start the FDI task if the task is stopped for less than 6 hours. If the task is stopped for more than 6 hours, the channel data has expired. Reset the synchronization progress as required and start the task again. If there are tables whose data is not fully collected before the task is stopped, all data of the tables will be collected again.
In addition, analyze the causes of the read-only state for database development optimization, or expand the disk space to prevent the problem from recurring.
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