You may be experiencing one of the issues below.
Production-optimized QuestDB configuration¶
If you can’t initially see your data through a
select SQL query straight
away, this is normal: by default the database will only commit data it receives
though the line protocol periodically to maximize throughput.
For dev/testing you may want to tune the following database configuration parameters as so:
# server.conf cairo.max.uncommitted.rows=1 line.tcp.maintenance.job.interval=100
The default QuestDB configuration is more applicable for a production environment.
For these and more configuration parameters refer to database configuration documentation.
You may not see data appear in a timely manner because you’re not calling
questdb.ingress.Sender.flush() often enough.
questdb.ingress.Sender class only provides auto-flushing based on
a buffer size and not on a timer.
Inspecting and debugging errors¶
Note that the ILP protocol does not send errors back to the client.
On error, the QuestDB server will disconnect and any error messages will be present in the server logs.
Asking for help¶
The best way to get help is through Slack.