https://pinot.apache.org/ logo
Join Slack
Powered by
# lp-pinot-poc
  • m

    Mayank

    10/03/2020, 10:29 PM
    Nice @User
  • x

    Xiang Fu

    10/03/2020, 10:30 PM
    also there is no latency bump up during segment build
  • m

    Mayank

    10/03/2020, 10:30 PM
    Seems like our settings worked very well
  • x

    Xiang Fu

    10/03/2020, 10:31 PM
    right
  • m

    Mayank

    10/03/2020, 10:31 PM
    👍👍
  • x

    Xiang Fu

    10/06/2020, 6:24 AM
    Hi @User , I’ve tested Pinot on JDK 11 with ZGC, the p99 latency is comparatively better than jdk8+ g1gc Below is the graph of switching it. Just for your reference: the docker image I’m using is
    apachepinot/pinot:0.6.0-SNAPSHOT-1126cac9b-20201002-jdk11
    the
    jvmOpts
    is
    -javaagent:/opt/pinot/etc/jmx_prometheus_javaagent/jmx_prometheus_javaagent-0.12.0.jar=80:/opt/pinot/etc/jmx_prometheus_javaagent/configs/pinot.yml -Xms24G -Xmx24G -XX:+UnlockExperimentalVMOptions -XX:+UseZGC -XX:+UseNUMA -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -Xlog:gc*:/opt/pinot/gc-pinot-server.log
  • x

    Xiang Fu

    10/06/2020, 6:25 AM
    However p999 is still around 1sec
  • a

    Andrew First

    10/12/2020, 1:24 PM
    @User that’s promising! how would i access the image via Helm?
  • x

    Xiang Fu

    10/12/2020, 3:36 PM
    you can directly update the image tag in the helm script
  • x

    Xiang Fu

    10/12/2020, 3:37 PM
    Copy code
    image:
      repository: apachepinot/pinot
      tag: latest
      pullPolicy: IfNotPresent
  • x

    Xiang Fu

    10/12/2020, 3:37 PM
    here you can change
    tag
    to
    0.6.0-SNAPSHOT-1126cac9b-20201002-jdk11
    👍 1
  • a

    Andrew First

    10/13/2020, 4:00 PM
    this is the result with those settings. still degrades after a couple of hours
  • a

    Andrew First

    10/13/2020, 4:00 PM
    Screen Shot 2020-10-13 at 11.59.46 AM.png
  • a

    Andrew First

    10/13/2020, 4:01 PM
    Screen Shot 2020-10-13 at 12.01.40 PM.png
  • a

    Andrew First

    10/13/2020, 4:02 PM
    Screen Shot 2020-10-13 at 12.02.33 PM.png
  • x

    Xiang Fu

    10/13/2020, 5:31 PM
    hmm
  • x

    Xiang Fu

    10/13/2020, 5:31 PM
    have you seen data movement happens to offline servers?
  • x

    Xiang Fu

    10/13/2020, 5:32 PM
    can you break that number of segments in Table to be server level metrics
  • a

    Andrew First

    10/14/2020, 3:34 PM
    hm, i don’t see that happening
  • a

    Andrew First

    10/14/2020, 3:34 PM
    it’s all showing as REALTIME
  • a

    Andrew First

    10/14/2020, 3:35 PM
    i thought it was configured to move completed segments to offline
  • a

    Andrew First

    10/14/2020, 3:35 PM
    i also see that a lot of segments are in a “bad” state
  • a

    Andrew First

    10/14/2020, 3:35 PM
    Screen Shot 2020-10-14 at 11.31.50 AM.png
  • a

    Andrew First

    10/14/2020, 3:37 PM
    if i click one of the bad segments, there’s no further information explaining why
  • a

    Andrew First

    10/14/2020, 3:37 PM
    Screen Shot 2020-10-14 at 11.37.24 AM.png
  • k

    Kishore G

    10/14/2020, 3:42 PM
    its a minor UI bug - it shows bad when its getting converted from consuming to ONLINE
  • k

    Kishore G

    10/14/2020, 3:42 PM
    https://github.com/apache/incubator-pinot/issues/6137
  • x

    Xiang Fu

    10/14/2020, 4:08 PM
    If all the segments are still on realtime nodes, then there is some issue there
  • x

    Xiang Fu

    10/14/2020, 4:08 PM
    from my benchmark, once segments are persisted, they will be moved to offline servers
  • x

    Xiang Fu

    10/14/2020, 4:09 PM
    do you have controller log or we can do a zoom call to look at this