Page MenuHomePhabricator

Fix an issue where daemons can stick in a pool
ClosedPublic

Authored by epriestley on Feb 28 2017, 4:10 PM.
Tags
None
Referenced Files
F14089720: D17433.diff
Sun, Nov 24, 12:49 PM
F14087498: D17433.id41917.diff
Sat, Nov 23, 10:06 PM
Unknown Object (File)
Sat, Nov 16, 10:38 AM
Unknown Object (File)
Mon, Nov 11, 2:34 PM
Unknown Object (File)
Mon, Nov 11, 1:25 AM
Unknown Object (File)
Fri, Nov 1, 2:53 PM
Unknown Object (File)
Oct 19 2024, 10:46 PM
Unknown Object (File)
Oct 15 2024, 6:11 PM
Subscribers
None

Details

Summary

Ref T12331. Root problem is the unset($daemon) just unsets a key in a local variable, rather than actually discarding the daemon.

Add some logging to make this more clear and clean up some %d vs %s stuff.

Test Plan
  • Ran a pool with bin/phd debug task --pool N, let it scale up, let it scale down, used bin/worker flood to add more tasks.
  • Before patch, the ghost daemons took up the slots in the pool.
  • After patch, the ghost daemons got removed properly and were replaced with fresh daemons.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/daemon/PhutilDaemonPool.php
181–188

Specifically, this is the actual bugfix.

🤷 ¯\_(ツ)_/¯

This revision is now accepted and ready to land.Feb 28 2017, 4:12 PM
This revision was automatically updated to reflect the committed changes.