Page MenuHomeDevCentral

Migrate Etherpad K/V store from MySQL to Redis
Closed, WontfixPublic

Description

Currently, the MySQL database for Etherpad has 629 771 rows in a store table, used by UeberDB as a K/V store.

Redis is a specialized server for such use, MySQL isn't really.

Plan

  1. Spin a redis container
  2. Shutdown Etherpad container
  3. Backup MySQL data
  4. Migrate Etherpad-Lite from MySQL to Redis (that's a Go program)
  5. Reconfigure Etherpad to use Redis
  6. Restart container

Authorization

As our Etherpad installation is shared, this needs an approval from @ledesillusionniste for Wolfplex.

Event Timeline

dereckson renamed this task from Migrate Etherpad K/V store from to Migrate Etherpad K/V store from MySQL to Redis.Aug 21 2016, 11:31

We discussed the issue on Wolfplex channel.

The acquisitariat container memory usage is back to 324 Mb, so it decreases the need to unclog the MySQL server.

Risks:

  • Etherpad + MySQL is battle-tested
  • Pads could be corrupted as a part of the process, and we wouldn't see that immediately.
  • our MySQL knowledge is superior than our Redis knowledge, so to monitor the first is currently easier

[ Those tasks have been identified as suitable for the next operations sprint. ]

dereckson claimed this task.

Without performance benchmark, the expected gain is not obvious.

If it's a matter of disk usage, Phabricator instances consume dozen of Gb in acquisitariat to store diff and files, so if we can live with that, we can live with Etherpad database too.