Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ep_mypads ep_mypads
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Framasoft
  • Etherpad
  • ep_mypadsep_mypads
  • Issues
  • #141

Closed
Open
Created May 09, 2017 by Yakulu@fabienMaintainer

Block requests before end of plugin initialization

On huge instances, if there are Etherpad crashes, MyPads may take some time be fully initialized, because Etherpad heavily uses database and data flushes before giving hand to plugins. This can lead to data corruption, as MyPads interface is usable before required in-memory indexes.

To prevent this trouble, we should use an in-memory initialization flag. All requests done before the flag has been set to true must return a generic error, for example "MyPads is loading, please wait".

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking