I've been investigating the issues with incomplete wiki creations resulting from JobQueue errors. I've been able to discover that Redis restarted during the time one such wiki was being created. Looking into it further, I discovered this restart was initiated by:
oom_reaper: reaped process 16298 (redis-server)
We should investigate why this is being done, and hopefully prevent oom_reaper from killing redis unless absolutely necessary. If that isn't possible, perhaps we should setup redundant redis with jobrunner4, but I'm not too certain as to the logistics of this.