Hi, we have a pinot setup on AWS EKS using helm, n...
# general
s
Hi, we have a pinot setup on AWS EKS using helm, now if I want to upgrade it to latest version 1.0.0 what is the process? I can see that even after doing helm update it is not showing new versions. Doc - https://docs.pinot.apache.org/basics/getting-started/kubernetes-quickstart GitHub link - https://github.com/apache/pinot/blob/master/helm/index.yaml (even this shows 2.7), does this mean that helm charts are not getting updated by Apache Pinot team?
Copy code
helm search repo pinot --versions
pinot/pinot             0.2.7           0.2.7           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.6           0.2.6           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.5           0.2.5           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.4           0.2.4           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.3           0.2.3           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.2           0.2.2           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.1           0.2.1           Apache Pinot is a realtime distributed OLAP dat...
pinot/pinot             0.2.0           0.2.0           Apache Pinot is a realtime distributed OLAP dat...
cc: @Ashwin Agalcha
x
Can you check what’s the Pinot docker image version using?
Helm usually won’t update the image version for upgrading.
For Pinot, you need to manually upgrade it. Usually it’s minor version one by one.
E.g 0.9.0->0.10->0.11->0.12.1->1.0.0
s
here is the snippet from my helm values file, so assuming it is 0.12
Copy code
image:
  repository: apachepinot/pinot
  tag: latest # release-0.12.0
  pullPolicy: Always # Use IfNotPresent when you pinged a version of image tag
@Xiang Fu
so if I want to upgrade pinot, can I put the tag
1.0.0
x
yes
if you are using latest , then I think you are already on latest after the whole cluster restart
You can put 1.0.0 to make the version consistent
s
yes sure, is there any way to verify the version from inside the pod also?
x
We build master branch nightly, so latest should be very recent one
👍 1
Yes, you can check the image sha then search it in dockerhub tag list
s
No that’s not what I meant, consider if I inside the pod (using kubectl exec), now do I check the version or the image? Because even the docker command is not present in the pod
x
There should be an api call for that
Can you try controller /version rest api
s
can’t see it here - https://docs.pinot.apache.org/users/api/controller-api-reference can you please share if you have it handy?
x
yeah, can you try
curl localhost:9000/version
when you enter into controller container
s
Copy code
curl localhost:9000/version
{"pinot-protobuf":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-kafka-2.0":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-avro":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-distribution":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-csv":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-s3":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-yammer":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-segment-uploader-default":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-batch-ingestion-standalone":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-confluent-avro":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-thrift":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-orc":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-clp-log":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-pulsar":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-azure":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-gcs":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-dropwizard":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-hdfs":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-adls":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-kinesis":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-json":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-minion-builtin-tasks":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-parquet":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187","pinot-segment-writer-file-based":"1.1.0-SNAPSHOT-f22de0a4be910af09556666df3aa44ae78d59187"}
does this mean we are already at 1.1.0?
x
yes, this is pretty close to latest
1.1.0-SNAPSHOT is before 1.1.0 release
s
okay 👍
this is about 2 month ago
s
1 more question, why helm chart version and app version are pointing to 0.2.7? Is this a bug or something?
@Xiang Fu ^
x
no, helm and pinot version are tracked separately
helm is for deployment, usually we don’t need much change and we can release based on demand
s
okay, but the app version that is shown here in the output is little confusing, that’s why I asked. Ideally the app version should point to pinot version but anyways thanks for ur help!! https://apache-pinot.slack.com/archives/CDRCA57FC/p1707135472717379
a
Thanks @Xiang Fu for your help!
x
You are right, we will fix that 🙂
Thanks for pointing this out
s
👍
a
@Xiang Fu I tried to run the window functioning in the above setup pinot as well as installed pinot locally with 1.0.0 version In local I am able to run my query In above pinot setup I am facing the error I have also enabled the use multi-stage engine
x
Hi @Amit Singh, The exception is just for window function or normal query won’t work as well? Also are you able to get the corresponding logs/stacktraces from broker or pinot-server-1 ?
a
The exception is coming for window function. The other queries are working fine Will share the logs from brokers
@Shubham Setia here
x
Ack. Cc : @Jackie for more details