I'm seeing the following logs fairly often in db.log:
2018-07-19 18:31:16 add_keys_merge failed: Eventloop.SigAlarm 2018-07-19 18:31:16 Key addition failed: Eventloop.SigAlarm
When these logs happen, the web interface becomes unresponsive and
sks db process spikes to 100% CPU. I guess this key merging is blocking the web interface from serving requests. I don't mind the CPU spike (it's only one thread), but the web unresponsiveness is getting me kicked out of the sks-keyservers.net pool frequently.
- Split key merging into a separate process from serving web requests. I don't mind running another process (maybe something like
sks keymerge) that will handle the high CPU spikes.
- Figure out a way to not spike the CPU so high and not block web requests when merging huge keys. No idea if this is possible given the current code architecture.
Related mailing list threads: