Ingested data not querable with weird partition name

Community
1

Hey, I am having an issue where data is ingested into QuestDB (8.3.3) and there seems to be no errors, but if I query the target table there is not recent data in the table;

select * from table_name order by timestamp desc limit 10

It return data of 2 days ago.

At closer inspection looking at the table partitions using:

SHOW PARTITIONS FROM table_name;

I see a partition that looks like this 2025-09-20T043453-898001 why would that be? And how do I fix it.

That seems to be the reason there is no data being returned from the above query for today and other date ranges. The last normal partition is 2025-09-20. I can query for the 20th and before without any issue.

I had a data issue on the server that I thought I resolved, but it caused this issue. It also seems to have some effect on CPU usage as the QuestDB instance seems to be constantly busy. Although SELECT * FROM wal_tables(); is not returning anything of note.

Any guidance or insights will be much appreciated.

2

For posterity, this was discussed on Slack. Looks like there were some inefficiencies with O3 writing that slowde things down on a small EBS drive. We also discussed double-checking symbol capacity as a potential proximate cuase.

Backlogs can be monitored using wal_tables() and checking the delta between sequencerTxn (what is committed) and writerTxn (what is visible for read).

There are also per-table ingestion metric charts available in the web console.