kaiquerass opened a new issue, #9032:
URL: https://github.com/apache/pinot/issues/9032

   I'm currently deploying a new pinot cluster and I was facing some issues 
while adding tables using [this 
guide](https://github.com/apache/pinot/blob/master/kubernetes/helm/pinot/pinot-realtime-quickstart.yml).
   
   After debugging it a lot, I guess I discovered the solution. Below are the 
problemas that I found:
   
   - The new helm package is missing on the repo. It's not possible to deploy 
minion stateless (or any update) using this repo as a helm repo.
   
   - Using stateless minion I got a connection refused on the controller while 
trying to add tables.
   
   - The combination of stateful minion and `latest` image, results in the 
errors below:
   Job logs: 
   `2022/07/08 14:22:23.062 INFO [AddTableCommand] [main] 
{"code":500,"error":"org.apache.pinot.shaded.org.apache.kafka.common.KafkaException:
 Failed to construct kafka consumer"}`
   Controller logs: 
   `Caused by: org.apache.pinot.shaded.org.apache.kafka.common.KafkaException: 
javax.security.auth.login.LoginException: No LoginModule found for 
org.apache.kafka.common.security.scram.ScramLoginModule`
   
   - Readiness and Liveness probes are not working on minion stateless, so it 
should be disabled on values file.
   
   **Resolution:** 
   We have another cluster and everything works fine, so I checked the 
differences and I realized the image used on this cluster was `latest:jdk-11`. 
Changing to this image I was able to create tables using `pinot-admin.sh` as 
described 
[here](https://github.com/apache/pinot/blob/master/kubernetes/helm/pinot/pinot-realtime-quickstart.yml).
   
   But, this solution only worked using stateful minion, stateless is still 
returning connection refused after changing the image.
   
   
   


-- 
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