applike-ss opened a new issue #12082:
URL: https://github.com/apache/druid/issues/12082


   ### Affected Version
   0.22.1
   
   ### Description
   I was trying to add the prometheus-emitter via the pull-deps command:
   `java -classpath "/opt/druid/lib/*" org.apache.druid.cli.Main tools 
pull-deps -c 
org.apache.druid.extensions.contrib:prometheus-emitter:${DRUID_RELEASE}`
   `$DRUID_RELEASE` was set to 0.22.1 via Dockerfile ARG.
   Also tried this in a separate docker container apache/druid:0.22.1 and 
executed `java -classpath "/opt/druid/lib/*" org.apache.druid.cli.Main tools 
pull-deps -c org.apache.druid.extensions.contrib:prometheus-emitter:0.22.1`.
   The execution takes ~5 minutes each time and in the docker build process it 
does not even seem to install the extension.
   ```
   time java -classpath "/opt/druid/lib/*" org.apache.druid.cli.Main tools 
pull-deps -c org.apache.druid.extensions.contrib:prometheus-emitter:0.22.1
   real    4m 45.06s
   user    0m 11.18s
   sys     0m 0.89s
   ```
   As i don't know much about pull-deps, i can't debug this and the 
documentation does not seem to include a debug or verbosity flag which could 
help me track down what is taking so long.
   I couldn't find a documentation on how to install the specific plugin 
either, so i assembled the path module/coordinate 
`org.apache.druid.extensions.contrib:prometheus-emitter` myself by browsing the 
maven repo.
   
   Would be great to know if the slowlyness is a mistake by me, if it is the 
tool or a temporary issue (though i could download the jar of the extensions 
really fast as it is less 100kb).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to