-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kong startup logs [error] still in larger deployments #14340
Comments
Straight up [error] logs throwing from 06:36:45 to 06:37:53 in those logs, little past a full minute. Related issue from prior: #13250 |
Is this like the sweet sauce that lets us know the errors are resolved at this point?
Where finally we see "ready to accept events" ? I guess the question is why the tons of errors prior and the full minute of it I suppose. Slow startup procedure stuff for larger Kong runtimes leading to early runtime initial error logs? |
Is there an existing issue for this?
Kong version (
$ kong version
)3.9.0
Current Behavior
I have brought this up in the past but still seeing it in our bigger proxy environment(more kong routes/services/plugins etc. Probably 5000+ proxies in total) But startup logs look like this, running Kong in traditional mode:
After these logs Kong is healthy and then starts regularly handling traffic. Still no idea why all the [error] logs in the startup phase of a larger Kong instance though?
Expected Behavior
No response
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: