Skip to content

Improve JDBC repository session clean-up job #1739

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

Open
vpavic opened this issue Nov 30, 2020 · 0 comments
Open

Improve JDBC repository session clean-up job #1739

vpavic opened this issue Nov 30, 2020 · 0 comments
Assignees
Labels
in: jdbc status: waiting-for-triage An issue we've not yet triaged type: enhancement A general enhancement

Comments

@vpavic
Copy link
Contributor

vpavic commented Nov 30, 2020

See #838 for background (and more specifically this comment).

The approach with a single SQL statement based session clean-up job has been historically been somewhat problematic, seeing several revisions to address issues seen with specific RDMBSs. The currently used statement is susceptible to deadlocks in MySQL/MariaDB and SQL Server.

We should consider improving the session clean-up job so that it:

  • is more robust, i.e. isn't susceptible to deadlocks
  • provides more insight into expired sessions (debug logs etc.)
  • doesn't execute on multiple nodes simultaneously in a cluster out-of-the-box
  • is easier to customize
@vpavic vpavic added type: enhancement A general enhancement status: waiting-for-triage An issue we've not yet triaged in: jdbc labels Nov 30, 2020
@vpavic vpavic added this to the 2.x milestone Nov 30, 2020
@vpavic vpavic self-assigned this Nov 30, 2020
@rwinch rwinch removed this from the 2.x milestone Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: jdbc status: waiting-for-triage An issue we've not yet triaged type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants