https://questdb.io logo
Title
d

Daniel Wedlund

05/24/2023, 7:23 AM
Hey, first huge thanks for QuestDB, it is awesome in many ways and have been using/prototyping around it for some time now and most of the time it just seems to work 🙂 Now, of course to something that is not working... When I run a query like:
select ct.timestamp as ct_ts, p.timestamp as p_ts from sensora as ct
ASOF JOIN sensorb as p
where p.timestamp between '2023-05-22T18:28:17.461000Z' and '2023-05-22T19:32:40.238000Z'
I get a silent error in the web-ui and the server logs give me the error:
2023-05-24T07:18:21.027359Z C i.q.c.h.p.JsonQueryProcessorState [861] error [msg=`could not mmap  [size=4799952, offset=0, fd=64977, memUsed=293434354166, fileLen=4800512]`, errno=12, q=`<the query above>`
I can without a problem query the two tables for the given time-range without a problem and the results are 150MB for one table and 24MB for the other table. I am a bit stumped on what to change/fix in terms of config to make this run successfully. My QuestDB instance runs inside docker under WSL2 on windows. The host machine has some 44 cores and 768GB RAM and is currently not running anything else that consumes those resources. Any ideas what to do/test?
d

Daniel Wedlund

05/24/2023, 7:42 AM
Thanks for that link, not sure why my google-fu did not lead me there 🙂 I will report back once I've tested it.
Fantastic, it works. Needed to fiddle some for the setting to be persisted, and in the end this section (Windows with Docker Desktop WSL 2 backend) https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#_set_vm_max_map_count_to_at_least_262144 In specific I opted for creating/modifying
%USERPROFILE%\.wslconfig
and set:
[wsl2]
kernelCommandLine = "sysctl.vm.max_map_count=262144"