Dear fellow etherpad-lite admins !
My server is suffering random disconnections with recommended setup and I don't know what to do.
I am relying on the dirtyDB, which doesn't introduce issues in my case. But now the db file size is huge! I really need to solve this problem coming days.
I have wrote a issue to their board (last summer), yet no answer and now stale.
https://github.com/ether/etherpad-lite/issues/5575
Maybe only me suffering this case? Any brainstorming/quick idea is appreciated!
@doohoyi Weird problem to have. I've had really good experience with etherpad and sqlite, running without issue for years. Maybe try that? Then, also could it be your webserver somehow? Have a look at the browser console log and see what it says when disconnects happen..
@rra oh sqlite+etherpad ?! that sounds great! since sqlite is also file based more similar to dirtydb, I guess, than mysql/redis/postgresql which is local network separate db servers.
btw, then sqlite db file grows huge... isn't it? how long did you run your etherpad and how large is the db file size?
dirtydb actually adds a lot of redundancies (really a lot) so.. my file is almost 10GB. :(
very interesting!
why did you choose sqlite at first place (for the backend of etherpad)?
do you especially prefer that db over others? or any situation to use that ? or any special reason ?
@doohoyi Hey, we chose sqlite to just have everything in one file for backups.
The instance has been running since 2018 or so and is used A LOT. The db size is 47GB. Not sure whether mysql or postgres will result in a smaller db btw. As I think it is more a structural problem.
If you don't want to have an endlessly growing db you will need to occassionally delete old pads. Etherpad is quite inefficient in terms of storage because every pad keeps a history of all revisions, which is the entire contents of the pad for each revision. So the same pad can be stored hundreds of times in the db.
Maybe, docker-way could be good to try & see. Whether if dockerized etherpad-lite have issue or not, will tell me where is the problem lies: in server, out of server = in the network.