[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] SKS scaling configuration
From: |
Todd Fleisher |
Subject: |
Re: [Sks-devel] SKS scaling configuration |
Date: |
Wed, 6 Mar 2019 22:54:49 -0800 |
Yeah, I thought it looked accurate. Attached is the full config for reference.
I’m still seeing issues where nginx frequently caches stats data from one of
the non-primary nodes even when I verify the primary node is responding when I
query it directly on it’s internal 10-net IP address. It’s puzzling for sure,
but has taken a back seat to trying to keep my servers stable lately as they’ve
been experiencing sustained periods of very high IO usage that are causing
instability. If anyone has nginx configurations to help combat the bad
key-induced instability, please do share.
nginx.conf
Description: Binary data
-T
> On Mar 5, 2019, at 1:20 AM, Kristian Fiskerstrand <address@hidden> wrote:
>
> don't recall the specifics of the snippets I sent over, but the above is
> correct, you do map definition at
> map $arg_op $upstream_server {
> "stats" sks_servers_primary;
> default sks_servers;
> }
>
> which is used for
>
> location /pks/lookup {
> proxy_cache backcache;
> proxy_ignore_headers Cache-Control "Expires";
>
> #proxy_cache_bypass $http_cache_control;
> add_header X-Proxy-Cache $upstream_cache_status;
> proxy_cache_valid any 10m;
> proxy_pass http://$upstream_server;
> proxy_pass_header Server;
> add_header Via "1.1 keys2.kfwebs.net";
> proxy_ignore_client_abort on;
> }
> }
>
> --
> ----------------------------
> Kristian Fiskerstrand
> Blog: https://blog.sumptuouscapital.com
> Twitter: @krifisk
> ----------------------------
> Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
> ----------------------------
> Corruptissima re publica plurimæ leges
> The greater the degeneration of the republic, the more of its laws
>
signature.asc
Description: Message signed with OpenPGP