• t

    theseusyang

    8 months ago
    @EHR Can you make more detailed description?
    t
    EHR
    +3
    7 replies
    Copy to Clipboard
  • x

    Xavier Witdouck

    8 months ago
    We deal with large amounts of financial time-series data, that sometimes undergoes revision / correction. Since it seems impossible to update or delete data in questdb, are there any recommended patterns for dealing with this scenario?
    x
    Nicolas Hourcard
    2 replies
    Copy to Clipboard
  • poling CHEN

    poling CHEN

    8 months ago
    Hello ~ Does anyone meet the problemhttps://github.com/questdb/questdb/issues/1741 Currently I still has no idea how to resolve it
    poling CHEN
    Miguel Arregui
    18 replies
    Copy to Clipboard
  • k

    Kendrick

    8 months ago
    Hi, my team got a segfault while using
    questdb 6.1.2 linux
    . Any idea on what's the issue? The error occurred when we tried using kafka connect with quest (although we had no issues for some time).
    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    #  SIGSEGV (0xb) at pc=0x00007f04b81b32d3, pid=131407, tid=131426
    #
    # JRE version: OpenJDK Runtime Environment AdoptOpenJDK (11.0.9.1+1) (build 11.0.9.1+1)
    # Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK (11.0.9.1+1, mixed mode, tiered, compressed oops, parallel gc, linux-amd64)
    # Problematic frame:
    # C  [libquestdb13985353930344026277.so+0x112d3]  find_latest_for_key(long, keys_reader const&, unsigned long, unsigned long, long, long, long, int, unsigned int)+0x113
    #
    # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/dev/.questdb/log/core.131407)
    #
    # If you would like to submit a bug report, please visit:
    #   <https://github.com/AdoptOpenJDK/openjdk-support/issues>
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #
    
    ---------------  S U M M A R Y ------------
    
    Command Line: -DQuestDB-Runtime-66535 -ea -Dnoebug -XX:+UnlockExperimentalVMOptions -XX:+AlwaysPreTouch -XX:+UseParallelOldGC --module-path=/home/dev/questdb-6.1.2-rt-linux-amd64/bin/questdb.jar -Djdk.module.main=io.questdb io.questdb/io.questdb.ServerMain -d /home/dev/.questdb
    
    Host: Intel(R) Xeon(R) CPU @ 2.80GHz, 4 cores, 15G, Ubuntu 20.04.3 LTS
    Time: Mon Jan  3 11:45:29 2022 UTC elapsed time: 5882.668639 seconds (0d 1h 38m 2s)
    
    ---------------  T H R E A D  ---------------
    
    Current thread (0x00007f04cc4f5800):  JavaThread "questdb-worker-2" [_thread_in_native, id=131426, stack(0x00007f0484cf9000,0x00007f0484dfa000)]
    
    Stack: [0x00007f0484cf9000,0x00007f0484dfa000],  sp=0x00007f0484df7f60,  free space=1019k
    Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C  [libquestdb13985353930344026277.so+0x112d3]  find_latest_for_key(long, keys_reader const&, unsigned long, unsigned long, long, long, long, int, unsigned int)+0x113
    
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    J 5730  io.questdb.griffin.engine.functions.geohash.GeoHashNative.latestByAndFilterPrefix(JJJJJJJJIIJIJJ)V io.questdb@6.1.2 (0 bytes) @ 0x00007f04c44537f4 [0x00007f04c4453740+0x00000000000000b4]
    J 18914 c2 io.questdb.tasks.LatestByTask.run()Z io.questdb@6.1.2 (70 bytes) @ 0x00007f04c3b64968 [0x00007f04c3b648c0+0x00000000000000a8]
    J 8053 c1 io.questdb.griffin.engine.table.LatestByAllIndexedRecordCursor.buildTreeMap(Lio/questdb/griffin/SqlExecutionContext;)V io.questdb@6.1.2 (834 bytes) @ 0x00007f04bd1bb50c [0x00007f04bd1b7c60+0x00000000000038ac]
    J 19353 c1 io.questdb.griffin.engine.table.LatestByAllIndexedFilteredAfterRecordCursor.buildTreeMap(Lio/questdb/griffin/SqlExecutionContext;)V io.questdb@6.1.2 (17 bytes) @ 0x00007f04bc6426ac [0x00007f04bc642560+0x000000000000014c]
    J 19351 c1 io.questdb.griffin.engine.table.AbstractRecordListCursor.of(Lio/questdb/cairo/sql/DataFrameCursor;Lio/questdb/griffin/SqlExecutionContext;)V io.questdb@6.1.2 (60 bytes) @ 0x00007f04bd0554e4 [0x00007f04bd055120+0x00000000000003c4]
    J 13861 c1 io.questdb.griffin.engine.table.LatestByAllIndexedFilteredAfterRecordCursorFactory.getCursor(Lio/questdb/griffin/SqlExecutionContext;)Lio/questdb/cairo/sql/RecordCursor; io.questdb@6.1.2 (6 bytes) @ 0x00007f04bc55543c [0x00007f04bc555080+0x00000000000003bc]
    J 5409 c2 io.questdb.cutlass.http.processors.JsonQueryProcessor.executeSelect(Lio/questdb/cutlass/http/processors/JsonQueryProcessorState;Lio/questdb/cairo/sql/RecordCursorFactory;Ljava/lang/CharSequence;)V io.questdb@6.1.2 (59 bytes) @ 0x00007f04c432a2b8 [0x00007f04c432a220+0x0000000000000098]
    J 20106 c2 io.questdb.cutlass.http.HttpConnectionContext.handleClientRecv(Lio/questdb/cutlass/http/HttpRequestProcessorSelector;Lio/questdb/cutlass/http/RescheduleContext;)Z io.questdb@6.1.2 (722 bytes) @ 0x00007f04c559482c [0x00007f04c5592ba0+0x0000000000001c8c]
    J 17845 c2 io.questdb.cutlass.http.HttpServer$1$$Lambda$282.onRequest(ILio/questdb/network/IOContext;)V io.questdb@6.1.2 (13 bytes) @ 0x00007f04c3b2ddec [0x00007f04c3b2dd60+0x000000000000008c]
    J 2511 c2 io.questdb.cutlass.http.HttpServer$1.run(I)Z io.questdb@6.1.2 (36 bytes) @ 0x00007f04c3baa8e0 [0x00007f04c3baa2e0+0x0000000000000600]
    J 2454% c2 io.questdb.mp.Worker.run()V io.questdb@6.1.2 (454 bytes) @ 0x00007f04c3b8ce54 [0x00007f04c3b8cd80+0x00000000000000d4]
    v  ~StubRoutines::call_stub
    k
    Brian
    2 replies
    Copy to Clipboard
  • k

    Konstantin Yovkov

    8 months ago
    Hello everyone, I'm trying to build and run QuestDB (by following the instructions from https://github.com/questdb/questdb/tree/master/core/README.md file). I noted a few (missing) things that probably worth mentioning: 👉 I needed to
    export NODE_OPTIONS=--openssl-legacy-provider
    in order to successfully execute mvn clean package -DskipTests -P build-web-console,build-binaries(the build-web-consoleprofile was needing this environment variable) I still cannot start the standalone jar, because I didn't have a
    conf/server.conf
    file in my data directory. After creating an empty file there, I receiver another error, saying that I'm missing another file, called
    mime.types
    . Any help to get QuestDB running (an updating the
    README.md
    file, if that is necessary) will be highly appreciated, Thanks
    k
    Brian
    +1
    29 replies
    Copy to Clipboard
  • Truc Nguyen

    Truc Nguyen

    8 months ago
    Hello to everyone. I’ve been running questDB on my server for a while now, but I recently encountered this issue when attempting to query the database; it happened for any query; I believe this is an issue with the questDB configuration, but I’m not sure which config parameters need to be changed to resolve this issue. Any idea on this? Thanks! cc @Bruno Haag
    Truc Nguyen
    Bruno Haag
    +4
    45 replies
    Copy to Clipboard
  • k

    Konstantin Yovkov

    8 months ago
    Hello everyone, Let's discuss this bug: https://github.com/questdb/questdb/issues/1726 Indeed, partitioning of tables, which don't have an explicit designated timestamp, does not make sense, but what about this case: Query:
    create table a (b int) partition by NONE;
    Should that be allowed or not? As I understand it, this is practically equivalent to
    create table a (b int);
    , because all the data will be appended to one file, which will never be partitioned by any criteria. But if the user explicitly specifies that there should be no partitioning on the table (by doing
    ...partition by NONE;
    ), then the compiler should point out that even though the user does not want any partitioning, the explicit usage of the
    partition by
    keyword(s) requires explicit designated timestamp. Thus, I think the
    create table a (b int) partition by NONE;
    should raise an error. What do you think?
    k
    Alex Pelagenko
    5 replies
    Copy to Clipboard
  • Bogdan

    Bogdan

    8 months ago
    Hello, what is wrong? Default configs, inserting a lot, 4 GB Memory, 2 CPU
    Bogdan
    Vlad
    8 replies
    Copy to Clipboard
  • jfcalvo

    jfcalvo

    8 months ago
    Hi, I have been taking a look to the HTTP configuration and I don’t see anything related with authentication/security what’s the common way to add security to HTTP requests to QuestDB?
    jfcalvo
    Vlad
    2 replies
    Copy to Clipboard
  • kmecpp

    kmecpp

    8 months ago
    Anyone know why I would get no response from the QuestDB server when trying to import a csv exactly like https://questdb.io/docs/develop/insert-data#rest-api ? requests.post() just completely hangs and I don't get any error. This happens with everything I'm trying... there's just no response or error. I can create a table fine (even though it takes over 2 seconds) so I know the server is at least working
    kmecpp
    Alex Pelagenko
    +1
    18 replies
    Copy to Clipboard