From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] issues with the mailing list
Date: Thu, 25 Mar 2021 15:48:37 -0400 [thread overview]
Message-ID: <6253876A-FF7D-4282-965F-3B4069C111DA@stanleylieber.com> (raw)
In-Reply-To: <5L9dOv9PILwOg1dZG9BhO2HCJucjv_AjzL84cqY2e-nU7yDeKQ4hQ_T8iZdEf--f7Z_EKodQiYDgYrOj1JqYUX876PzfBRP29ByPHnCE7RA=@protonmail.com>
On March 25, 2021 2:07:35 PM EDT, kemal <kemali13@protonmail.com> wrote:
>your message got sent late but latest messages are coming much faster compared
>to older messages.
>
>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>On Thursday, March 25, 2021 2:17 PM, Stanley Lieber <sl@stanleylieber.com> wrote:
>
>> On March 25, 2021 9:48:40 AM EDT, Stanley Lieber sl@stanleylieber.com wrote:
>>
>> > 1ess; walk /mail/queue|wc -l 6906
>> > divide this number roughly in three to get the number of presently undelivered messages (to all lists; this machine serves all/only 9front/cat-v/werc lists). of those, the vast majority are transient dns lookup failures for good domains. we alleviated this somewhat already by extending the lookup timeout, but clearly something else is going on.
>> > all of this started when I moved the server back to 9cloud from ramnode. the first thing we noticed was the default setup hammered the now non-ssd disk by launching runq every time it processed a message. this brought the whole machine to a crawl (this machine also serves the websites -- people complained). that was solved by parallelizing a limited number of runqs and launching them periodically from cron. the side effect of this is exposing all kinds of weirdness that was previously masked by the never-ending blast of runqs, which, in spite of transient failures, always eventually clears out the queue.
>> > I'm not yet sure why the transient dns failures are happening.
>> > sl
>>
>> the server has now been configured to run its own resolver. we'll see if this results in fewer transient lookup failures.
>>
>> sl
>
>
>
1ess; date
Thu Mar 25 15:47:40 EDT 2021 1ess; walk /mail/queue|wc -l
5575
next prev parent reply other threads:[~2021-03-26 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 10:34 kemal
2021-03-25 10:42 ` hiro
2021-03-25 13:48 ` Stanley Lieber
2021-03-25 14:17 ` Stanley Lieber
2021-03-25 18:07 ` kemal
2021-03-25 19:48 ` Stanley Lieber [this message]
2021-03-25 17:31 ` kemal
2021-03-25 17:36 ` Philip Silva
2021-03-25 18:36 ` toby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6253876A-FF7D-4282-965F-3B4069C111DA@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).