Opened 10 years ago

Closed 2 years ago

Last modified 9 months ago

#6991 closed enhancement (fixed)

Update registrar to use start_watching_system() API

Reported by: anevilyak Owned by: bonefish
Priority: low Milestone: R1/beta2
Component: Servers/registrar Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


Currently the registrar does a polling sanity check in order to detect teams which have gone away without unregistering properly (i.e. in the case where a team is killed/crashes rather than quitting normally). This could be eliminated by instead using the new start_watching_system() call to monitor for team creation/destruction.

Change History (5)

comment:1 by anevilyak, 10 years ago

If no one beats me to it, I'll try to deal with this over the weekend sometime, just wanted to file the ticket so it's not forgotten.

comment:2 by waddlesplash, 2 years ago

That's a long weekend... :)

I might take a stab at this. Anything else that might have changed in the past 8 years that I'd need to know?

comment:3 by tqh, 2 years ago

I'll see if I can take a stab at this, I was checking what is using cpu at idle and 2% seems to be registrar timer_thread, and that seems to be this. Changing it from 1s to 5s takes that down to 0.1% cpu. Checked with top.

Some reference for how to do it (from waddlesplash):

comment:4 by waddlesplash, 2 years ago

Resolution: fixed
Status: newclosed

Fix merged in hrev52796.

comment:5 by nielx, 9 months ago

Milestone: R1R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.