Skip to content
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

Lua batch_queue failed to process entries #10103

Closed
1 task done
jmicceri opened this issue Jan 12, 2023 · 3 comments
Closed
1 task done

Lua batch_queue failed to process entries #10103

jmicceri opened this issue Jan 12, 2023 · 3 comments
Assignees
Labels
core/pdk pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc...

Comments

@jmicceri
Copy link

jmicceri commented Jan 12, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

3.1.1

Current Behavior

After upgrading to version 3.1.1 (up from 3.0.2) we starting seeing millions (~165M) of the following warning in our Kong/nginx logs:

3824#0: *31876612 [lua] batch_queue.lua:183: failed to process entries: nil

After downgrading back to 3.0.2, the warnings went away. Are there other changes that need to be made on our end as part of the upgrade? Checking the upgrade notes, I don't see any other packages or steps that need to be taken

Expected Behavior

Kong should be able to process all entries and there shouldn't be an increase in the number of warning logs produced

Steps To Reproduce

1. Change Kong version from 3.0.2 → 3.1.1
2. Deploy Kong service (running as docker container)
3. Check NGINX logs and view increase in WARN level messages

Anything else?

No response

@hanshuebner hanshuebner self-assigned this Jan 12, 2023
@hanshuebner
Copy link
Contributor

Hi @jmicceri,

can you share a couple of details of your configuration? We're particularly interested in the plugins that you're using and the request volume.

Thank you!
Hans

@jschmid1 jschmid1 added the pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... label Jan 17, 2023
@hanshuebner
Copy link
Contributor

@jmicceri We've located the source of the problem and a fix is already available on the master branch (0eae6b9). It will be included in the next releases.

@locao
Copy link
Contributor

locao commented Jan 24, 2023

Closing this issue as it was fixed by #10126.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core/pdk pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc...
Projects
None yet
Development

No branches or pull requests

4 participants