[tor-relays] Overloaded state indicator on relay-search

Mon Sep 27 14:23:34 UTC 2021

 George,
The referenced support article provides recommendations as to what might be causing the overloaded state, but it doesn't provide the metric(s) for how Tor decides whether a relay is overloaded. I'm trying to ascertain the later.
I would assume the overloaded state metric(S) is/are a maximum timeout value and/or reoccurrence value, etc.
By knowing what the overloaded state metric is, I can tune my Tor relay just short of it.
Thank you for your reply.
Respectfully,

Gary

    On Monday, September 27, 2021, 2:44:35 AM PDT, Georg Koppen <gk at torproject.org> wrote:  

 Gary C. New via tor-relays:
>  Hiro,
> Presently, I'm seeing a similar issue. On my laptop, I'm observing an overloaded status for my relay. However, the same relay shows a green status on my phone.
> Do you do any user-agent detection?
> I'm still interested in those magic numbers, which determine whether a relay has reached an overloaded state.

Which numbers do you mean? Is there anything missing from the support
article[1] you feel should be there?

Georg

[1] https://support.torproject.org/relay-operators/relay-bridge-overloaded/

> Thank You.
> Respectfully,
> 
> Gary
> 
>    On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro <hiro at torproject.org> wrote:  
>  
>  Hi,
> I went back in history and tried to find out whenever your node
> FriendlyExit1 was overloaded. I couldn't find the exact descriptor.
> 
> One thing I can think of is that on the 22nd when I deployed this I
> noticed a few typos in the code and had to make a second release. Maybe
> something was cached for a while and you what you were accessing from
> mobile was the buggy page.
> 
> If it happens again there are two buttons at the end of the page where
> you can see the latest server and extra-info descriptors. If you
> download the server one you would be able to verify that there is a
> "overload-general" field in there. If there isn't we have a bug :).
> 
> Please let me know if this happens again.
> 
> Cheers,
> -hiro
> 
> On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote:
>> Hey hiro, thanks!
>>
>> I've also attached some screenshots too if it helps (sorry, I should have done that before). I had first noticed this around 3:45 PM CST on September 23.
>>
>> - The Friendly Exit Node Family
>>
>> Sent with ProtonMail Secure Email.
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>
>> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro <hiro at torproject.org> wrote:
>>
>>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote:
>>>
>>>> This looks like an awesome feature! I super appreciate it.
>>>>
>>>> Random question though (and I'm the first to admit I may be doing something wrong), I notice that on Mobile it says my relays are overloaded however when I view it on a normal computer I don't get the overloaded indicator. I've tried refreshing multiple times but getting the same results. Is anyone seeing the same thing?
>>>
>>> Hi,
>>>
>>> could you let me know when you accessed the page via mobile approximately?
>>>
>>> I'll try to check if any of your relays were overloaded in the past.
>>>
>>> When a node is overloaded the state is kept for 72 hours.
>>>
>>> Cheers,
>>>
>>> -hiro
>>>
>>>> Family Members:
>>>>
>>>> F01E382DA524A57F2BFB3C4FF270A23D5CD3311D
>>>>
>>>> 623CCCC1A1370700DD03046A85D953D35CAB5C21
>>>>
>>>> F9A28AB71D7E4E446308641A556EA53BA55FCB50
>>>>
>>>> 23F74D581DE92AC59D3527DE4D448E036139D81E
>>>>
>>>> A00E900534DFF76371064C03714753EAF8B88820
>>>>
>>>> C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5
>>>>
>>>> -  The Friendly Exit Node Family
>>>>
>>>> Sent with ProtonMail Secure Email.
>>>>
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>
>>>> On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro hiro at torproject.org wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> One of our goals with our current performance work is to reduce the
>>>>>
>>>>> overload of relays in the network. The implementation of proposal 328[1]
>>>>>
>>>>> a while back made different overload indicators available to relay
>>>>>
>>>>> operators and since a couple of weeks ago those can be tracked via
>>>>>
>>>>> Onionoo[2] as well.
>>>>>
>>>>> As we know that a lot of our relay operators use relay search to check
>>>>>
>>>>> for the health of their relays, we have launched a new feature there,
>>>>>
>>>>> too, to help them know when their relays are overloaded.
>>>>>
>>>>> When a relay is in the overloaded state we show an amber dot next to the
>>>>>
>>>>> relay nickname.
>>>>>
>>>>> Currently we are counting between 50 and 80 overloaded relays and
>>>>>
>>>>> between 10 and 20 overloaded bridges.
>>>>>
>>>>> The overloaded state is reached when one or many of the possible load
>>>>>
>>>>> metrics have been triggered. When this happens we show it for 72 hours
>>>>>
>>>>> after the relay has recovered [3]. Note, though, that not all of the
>>>>>
>>>>> exposed overload metrics are triggering the overload indicator on relay
>>>>>
>>>>> search yet.
>>>>>
>>>>> If you noticed your relay is overloaded, please check the following
>>>>>
>>>>> support article to find out how you can recover to a "normal" state:
>>>>>
>>>>> https://support.torproject.org/relay-operators/relay-bridge-overloaded/
>>>>>
>>>>> Let us known how you find this new feature.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> -hiro
>>>>>
>>>>> [1]
>>>>>
>>>>> https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md
>>>>>
>>>>> [2]
>>>>>
>>>>> https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html
>>>>>
>>>>> [3] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637
>>>>>
>>>>> tor-relays mailing list
>>>>>
>>>>> tor-relays at lists.torproject.org
>>>>>
>>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>>
>>>> tor-relays mailing list
>>>>
>>>> tor-relays at lists.torproject.org
>>>>
>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>> tor-relays mailing list
>>>
>>> tor-relays at lists.torproject.org
>>>
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays at lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>  
> 
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

_______________________________________________
tor-relays mailing list
tor-relays at lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20210927/80ca1249/attachment-0001.htm>