|
From: | Todd Fleisher |
Subject: | Re: [Sks-devel] Peering Issues - High IO ending with Eventloop.SigAlarm always occur with 1 peer |
Date: | Wed, 10 Oct 2018 11:00:44 -0700 |
Hi All, I wanted to follow up on this and add some new data points. I tried building some new SKS instances based on a more recent dump (specifically 2018-10-07 from https://keyserver.mattrude.com/dump/) and found those instances were plagued by the same issue when I began peering with my existing instances. When I re-built the new instances from an older dump (specifically 2018-10-01 from the same source), the issues went away. This seems to imply some problematic data was introduced into the pool during the first week of October that is causing the issues. I found an existing issue logged about this behavior @ https://bitbucket.org/skskeyserver/sks-keyserver/issues/61/key-addition-failed-blocks-web-interface For now, I’m able to keep my instances stable by building them from the earlier 2018-10-01 dump and not adding the second peer to my membership file. I would like to better understand why this is happening and figure out how to go about fixing it, in part so I can begin peering with more servers to improve the mesh. -T
|
signature.asc
Description: Message signed with OpenPGP
[Prev in Thread] | Current Thread | [Next in Thread] |