sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] Another poison-key?


From: Kim Minh Kaplan
Subject: Re: [Sks-devel] Another poison-key?
Date: Sat, 02 Feb 2019 22:14:40 +0000

Martin Dobrev writes:

> 2019-01-29 14:20:05 1 hashes recovered from <ADDR_INET [188.138.x.x]:23371>
> 2019-01-29 14:20:05     7594FE72B3E93A0350D9950B926F81A7
> 2019-01-29 14:20:11 1 keys found
> 2019-01-29 14:20:16 Requesting 1 missing keys from <ADDR_INET
> [188.138.x.x]:23371>, starting with 7594FE72B3E93A0350D9950B926F81A7
> 2019-01-29 14:20:54 1 keys received
> 2019-01-29 14:21:22 Applying 2 changes
> 2019-01-29 14:21:22 Adding hash 7594FE72B3E93A0350D9950B926F81A7
> 2019-01-29 14:21:22 Del'ng hash A3875A8B77A3ABADE2B855A8FCABC73D
> 2019-01-29 14:22:29 add_keys_merge failed: Eventloop.SigAlarm
> 2019-01-29 14:22:38 Key addition failed: Eventloop.SigAlarm
>
> My best guess is that this key has been poisoned. Do you experience
> similar issues? All my server nodes (7+ in total) are suffering atm.

This issue also reached my server. That prompted me to investigate. It
was caused by a huge key (34MB) that was taking to long to store in the
database. At first I thought that increasing wserver_timeout would allow
the key in. It turns out to be the wrong knob: increasing command_timeout
did it.

Of course I realize this is merely sweeping the real issue under the
carpet. I just hope this will allow us to sustain the network some more.

Kim Minh.



reply via email to

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