benrush
11/03/2022, 3:47 AMCairoConfiguration
just like server.conf
so that we could understand how to configure the embedded QuestDB instanceđWCKD
11/03/2022, 8:37 AMSuri Zhang
11/03/2022, 8:52 AMNewskooler
11/03/2022, 11:37 AMJustin Bojarski
11/03/2022, 1:42 PMNewskooler
11/03/2022, 7:19 PMcould not mmap [Size=6720, offset-0. fd-65133, memUsed= 16222810218, fileLen=8192]
I remember there was a way to âfixâ this in the config by increasing some of the default values.
Can you please point me out to where I should read more about this and what in particular seems to be the problem here đ€Shubham Jain
11/04/2022, 8:04 AM/var/spool/mail/root
and below are the contents -
From root@ip-172-31-24-139.ap-south-1.compute.internal Fri Nov 4 06:05:02 2022
From: "(Cron Daemon)" <root@ip-172-31-24-139.ap-south-1.compute.internal>
To: root@ip-172-31-24-139.ap-south-1.compute.internal
Subject: Cron <root@ip-172-31-24-139> /etc/cron.daily/logrotate
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
error: Ignoring questdb because of bad file mode - must be 0644 or 0444.
any thoughts on this ?javier ramirez
11/04/2022, 10:54 AMMichael
11/04/2022, 7:17 PMNicolas Hourcard
11/04/2022, 10:19 PMAhmad Abbasi
11/06/2022, 1:39 AMNov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # A fatal error has been detected by the Java Runtime Environment:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # SIGSEGV (0xb) at pc=0x00007f7e4c86e460, pid=114765, tid=114954
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # JRE version: OpenJDK Runtime Environment Corretto-11.0.17.8.1 (11.0.17+8) (build 11.0.17+8-LTS)
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # Java VM: OpenJDK 64-Bit Server VM Corretto-11.0.17.8.1 (11.0.17+8-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # Problematic frame:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # J 3786 c2 io.questdb.cairo.vm.api.MemoryCR.getLong(J)J io.questdb@6.5.4 (44 bytes) @ 0x00007f7e4c86e460 [0x00007f7e4c86e420+0x0000000000000040]
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # An error report file with more information is saved as:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # //hs_err_pid114765.log
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # If you would like to submit a bug report, please visit:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # <https://github.com/corretto/corretto-11/issues/>
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: questdb.service: main process exited, code=killed, status=6/ABRT
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: Unit questdb.service entered failed state.
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: questdb.service failed.
Ahmad Abbasi
11/06/2022, 1:40 AM6.5.4
Nicolas Hourcard
11/07/2022, 8:46 AMJone Qiang
11/07/2022, 9:28 AMMichal Stovicek
11/07/2022, 1:07 PMasync command/event queue buffer overflow
Can you suggest what to do about it? Thanks! (Using version 6.5.3)Pei
11/08/2022, 9:06 AMHà Hữu
11/08/2022, 10:55 AMWeibo Lei
11/09/2022, 2:43 AMSELECT * FROM kline_item WHERE stock_id = '603501' and market_type = '1' and k_type = '6' and candle_mode = '2' order by market_date desc limit 500;
it may spend more than 1 second to the first time query.
500 rows in 4.35s
Execute: 4.28sNetwork: 68.74msTotal: 4.35s
and It normally spends 600ms in the next couple of times with the same SQL.
the schema of the table is:
CREATE TABLE kline_item(
market_date TIMESTAMP,
update_date TIMESTAMP,
market_date_int int,
update_date_int int,
market_type SYMBOL CAPACITY 4 NOCACHE INDEX,
stock_id SYMBOL CAPACITY 28000 NOCACHE INDEX,
k_type SYMBOL CAPACITY 5 NOCACHE INDEX,
highest_price double,
lowest_price double,
open_price double,
close_price double,
trade_val double,
trade_amount long,
change_amount double,
change_pct double,
exchange_ratio double,
candle_mode SYMBOL CAPACITY 2 NOCACHE INDEX,
up_or_down_limt byte,
ma60 double,
ma120 double,
ma250 double,
state byte,
create_time TIMESTAMP,
update_time TIMESTAMP
), INDEX(stock_id) TIMESTAMP(market_date)
PARTITION BY DAY;
ps: I index the fields like 'market_type','stock_id','k_type' and 'candle_mode' because I want to make the query faster during the query.
How can I speed up my query speed?Jaromir Hamala
11/09/2022, 1:10 PMWCKD
11/09/2022, 3:29 PMWeibo Lei
11/09/2022, 3:34 PMNicolas Hourcard
11/09/2022, 4:40 PMBenjamin Böck
11/10/2022, 9:54 AMHolger
11/10/2022, 3:19 PMHolger
11/10/2022, 3:20 PMHolger
11/10/2022, 3:20 PMHolger
11/10/2022, 3:20 PMcl
11/10/2022, 5:45 PMJan Pojer
11/10/2022, 10:12 PMNicolas Hourcard
11/10/2022, 10:30 PMNicolas Hourcard
11/10/2022, 10:30 PM