You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2022/11/30 10:24:25 UTC

[GitHub] [skywalking] zshrine opened a new issue, #10063: [Feature] Option to edit liveness/readiness probe of oap in helm chart

zshrine opened a new issue, #10063:
URL: https://github.com/apache/skywalking/issues/10063

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   The first replica of the oap container can take quite a while to startup. I have tried modifying the jvm options to a higher memory but the problem still persist. We can edit the deployment after doing a helm install/upgrade but would be much preferable if we can edit it directly as value. 
   
   Also, is there any suggestions on how we can speed up the startup ? Or could it be some setting on our end that is causing the slow startup?
   
   ### Use case
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: notifications-unsubscribe@skywalking.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [skywalking] kezhenxu94 commented on issue #10063: [Feature] Option to edit liveness/readiness probe of oap in helm chart

Posted by GitBox <gi...@apache.org>.
kezhenxu94 commented on issue #10063:
URL: https://github.com/apache/skywalking/issues/10063#issuecomment-1331985722

   At the very first run, OAP needs to wait for OAP init job to finish, while the init job needs to wait for the storage's readiness. 
   
   What do you mean it's slow? Do you measure from the OAP is running or from the OAP is created?


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [skywalking] wu-sheng closed issue #10063: [Feature] Option to edit liveness/readiness probe of oap in helm chart

Posted by GitBox <gi...@apache.org>.
wu-sheng closed issue #10063: [Feature] Option to edit liveness/readiness probe of oap in helm chart
URL: https://github.com/apache/skywalking/issues/10063


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org