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
Submit a service ticket to the DWS customer service.
After the database service is restored, you can directly start the task if the FDI task is stopped for less than 6 hours. If the FDI task is stopped for more than 6 hours, the data in the stream has expired. You need to reset the synchronization progress based on site requirements and start the task again. If a table whose full data is not collected exists before the task is stopped, the full data of the table will be collected again.
In addition, DWS engineers need to analyze the cause of the read-only state, promote database-based service development for optimization, or expand the disk space to prevent the problem from recurring.
Last Article: Inserted Data Violates the Non-null Constraint
Next Article: Speed of Writing Data to DWS Becomes Slower
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.