Hi everyone, I am having a bit of trouble truncating data from a table as inserts are taking place simultaneously into the table via TCP/ILP.
I get the following error: table 'table_name' could not be truncated: : table busy [reason=tcpIlp]
Apart from stopping the service to truncate the data is there another way that this can be achieved?
are you able to share your use case at a higher level?
09/30/2022, 4:22 PM
@… so I deployed a service that persists metrics to quest db, using TCP/ILP today, to a table that is partitioned by day. But that service started sending incorrect metrics, due to which we decided to erase all the data persisted to that table today, and redeploy the service with a fix. But as mentioned we could not truncate any data as the table writer was busy and could not drop the latest partition created as well.