How do you isolate broken pads?

[gedion]

Hello,

We continue to have errors that cause pads to break and cause server restarts, affecting everyone else that maybe working at that time. its like 1 in 20 pads that break but the problem is exacerbated by users continuously requesting for a broken pad.

What we would like to do is be able to detect a broken pad and hide it from user before a user makes subsequent requests.

The is a temporary solution. Any idea?

[JohnMcLear]

Are you running any plugins? Have you tried https://github.com/ether/etherpad-lite/blob/master/bin/checkPad.js ? The usual cause of the problems are pad breaks caused by plugins.

[Wikinaut]

How to isolate pads ?

Well, there are some ideas, but no implementations yet.

I suggested in #192 (comment) an admin panel as plugin and in https://github.com/ether/etherpad-lite/wiki/FAQ a pruning function ("How can I prune the database so that only the last n "revisions" are kept ? Both var/dirty.db and MySQL grow quickly. Production instances should use MySQL or some mature database storage mechanism. Dirty.db is not really designed for production and is just included so you can easily get started with Etherpad Lite. Etherpad Lite has no automated database pruning (removal of older revisions) mechanism.")

[gedion]

@johnyma22, Yes we are running some plugins. But I don't believe they are the cause. Thanks for the checkPad script. Will give it a try.

@Wikinaut, We use Oracle and we do have an archiving mechanism. We keep our working table to about 300k row entries.