[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Another Poison Key?

From: Simon Lange
Subject: Re: [Sks-devel] Another Poison Key?
Date: Fri, 18 Jan 2019 12:17:26 +0100
User-agent: Roundcube Webmail/1.3.8

Am 18.01.2019 11:01, schrieb Andrew Gallagher:
On 18/01/2019 06:09, Gabor Kiss wrote:
Is "... while gossip disabled. Ignoring." is normal?

Yes. SKS is single-threaded, so while it is in the middle of a task it
politely ignores incoming network requests.

And how do we tell sks to use more than ONE instance for the SAME database?! Because ONE single thread is a pretty big bottleneck problem. And i could not discover any sksconf or runtime option which spawns more than one sks instance to run more stable in a productive way.

Any chance that sks will be fixed some day? allowing using a better databasesystem for performance and stability, a better scheduler for better processing requests and a proper logging which gives answers and does not produce new questions. e.g. if a process stalls and sks is able to give an error message, why doesnt it give the cause of the problem as well? especially if debug and level is set to max? currently is pretty hard to investigate causes for sks-problems. its like blackbox-debugging. ;)


PPCIS - Project Leader

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]