Skip to content

No operations are allowed after the statement is closed after upgrading from 2.0.10-1 to 2.6.3-1 #4857

@tijoytom

Description

@tijoytom

We are upgrading proxysql from version 2.0.10-1 to 2.6.3-1 and started noticing
"No operations are allowed after the statement is closed" from clients. These are relatively long-running jobs that hold onto the connection. This issue specifically popped up after upgrading proxysql.

Below are our current setting wait-timeout settings
proxysql MySQL-wait_timeout : 8 hours
MySQL wait-timeout : 3 minutes

We increased the wait timeout on the MySQL side to 30 minutes, and the exceptions disappeared.
This is not the ideal config, but any pointers that explain the difference in behavior
between proxysql 2.0.10-1 and 2.6.3-1 will be beneficial.

Thanks for the help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions