We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Solved. The root cause is at crateDB. When the hard disk exausted, the crateDB is down and every table are set with readonly. The read-only blocks are not automatically removed from the tables even after the disk space is freed and the threshold is undershot.

Everything is OK after I set the readonly flag to false with the following command in crateDB:

SHOW CREATE TABLE <tableName>;
ALTER TABLE <tableName> SET ("blocks.read_only_allow_delete" = FALSE);

More details are described at: https://stackoverflow.com/questions/61575239/fiware-quantumleap-sanity-check-failed-quantumleap-cant-get-changed-data-from