Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
core
core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 234
    • Issues 234
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hubzilla
  • corecore
  • Issues
  • #1487

Closed
Open
Opened Nov 12, 2020 by Mark Nowiasz@mnowiasz

Large queues are killing the mysql server

Related to #1486 (closed) - I was trying to find out the problem and found out that large queues where causing huge amounts of UPDATE statement filling up the processlist, running for more than 2000 seconds. I've attached a SHOW PROCESSLIST

While there was already a queue problem in 4.6, it apparently has grown much much more worse in 5.0, resulting in a non-responsive hub due to the database filling up with queries. The only chance to counter that is restarting the mysql and deleting the outq. Guys, you really have to fix the queue processing.

processlist.txt

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hubzilla/core#1487