➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

作者 vinay.sajip
收信人 Oleg Nykolyn, remi.lapeyre, serhiy.storchaka, vinay.sajip
日期 2020-09-02.11:32:11
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1599046331.26.0.0718825873111.issue40352@roundup.psfhosted.org>
In-reply-to
内容
> It is enough to reopen the socket and send the current message again.

A common reason for connection failure in SocketHandler is the other end going offline for some reason. The offline period can often be measured in seconds to hours, or even longer. The current strategy is to retry connection, but on the next logging call, and with an exponential backoff.

Otherwise, if the remote end goes down and you keep retrying to connect on the same call, the handler would keep trying to connect and failing, and this could slow things down.
历史
日期 用户 动作 参数
2020-09-02 11:32:11vinay.sajip修改recipients: + vinay.sajip, serhiy.storchaka, remi.lapeyre, Oleg Nykolyn
2020-09-02 11:32:11vinay.sajip修改messageid: <1599046331.26.0.0718825873111.issue40352@roundup.psfhosted.org>
2020-09-02 11:32:11vinay.sajip链接issue40352 messages
2020-09-02 11:32:11vinay.sajip创建