Hey Guys, Seeing this error during pinot server a...
# troubleshooting
y
Hey Guys, Seeing this error during pinot server and broker startup
Copy code
Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : /opt/pinot/etc/jmx_prometheus_javaagent/jmx_prometheus_javaagent.jar
I can see a similar issue was reported here - https://github.com/apache/pinot/issues/16283 I don't think the fix was applied to this tag -> https://hub.docker.com/layers/apachepinot/pinot/1.3.0/images/sha256-27d64d558cd8a90efdf2c15d92dfd713b173120606942fd6faef9b19d20ec2dd Can someone pls look into this ?
m
@Xiang Fu ^^
x
Yes, I will rebuild the image
thanks 2
This is done
m
Thanks @Xiang Fu
y
Hey @Xiang Fu / @Mayank, It's generally not recommended to update a tag with a different image. Is it recommended for us to maintain our own copy of the images to not run into such issues in the future ?
x
no, this is rarely happen and the image should be fixed
the image tag is aligned with the pinot release tag
unless there is a pinot issue and worth a fix for 1.3.1, then there will be an image of 1.3.1 tag.
r
@Xiang Fu Do we have any Image Tag policy in pinot that we can follow to distinguish between mutable (re-taggable) and immutable (fixed) image tags.
@Mayank Can you please help here. Actually we are going live in production with Apache Pinot and understanding the tags ploicy is crucial for us so that our production environment be stable.
x
@Rohini Choudhary I drafted a policy which is not officially approved, but reflect the status quo:
Copy code
Apache Pinot Docker Image Publishing Policy

This policy outlines the guidelines for publishing Docker images for Apache Pinot:

Image Immutability:

Once a Docker image tag is published, it should generally remain immutable. However, if an image is found to be unusable, compromised, or contains significant vulnerabilities, the community may collectively decide to replace the problematic image with a new build under the same tag.

Build Process Issues:

If there are issues specific to the Docker build process (e.g., Dockerfile configuration errors, missing dependencies in the image, security patches for base images), it is permissible to publish a corrected Docker image with the same Pinot software version under the original tag without adding suffixes.

Apache Pinot Software Issues:

Issues discovered in the Apache Pinot software itself must not trigger a rebuild or republish of existing Docker image tags.

Software-related issues must instead be resolved through a new Apache Pinot software release. A new Docker image corresponding to the new Pinot version will be naturally generated and tagged accordingly (e.g., from 0.14.0 to 0.14.1).

Version Tagging:

Docker images should follow semantic versioning consistent with Apache Pinot releases.

Any Dockerfile-specific updates or corrections without Pinot software changes should be published under the original version tag.
r
Thanks for the clarification.