From 83a8cf6d258797891e7a1a75ff0938bd93f96ccd Mon Sep 17 00:00:00 2001 From: Dave Horton Date: Sun, 4 Jan 2026 12:23:26 -0500 Subject: [PATCH] SIGUSR1 should cause fs to commence drying up calls but do not exit when call count reaches zero (#1486) --- lib/utils/sbc-pinger.js | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/lib/utils/sbc-pinger.js b/lib/utils/sbc-pinger.js index 3b4d6f17..ec6c453e 100644 --- a/lib/utils/sbc-pinger.js +++ b/lib/utils/sbc-pinger.js @@ -120,17 +120,8 @@ module.exports = (logger) => { } pingProxies(srf); - // if we have zero calls, we can complete the scale-in right - setTimeout(() => { - const calls = srf.locals.sessionTracker.count; - if (calls === 0) { - logger.info('scale-in can complete immediately as we have no calls in progress'); - process.exit(0); - } - else { - logger.info(`${calls} calls in progress; scale-in will complete when they are done`); - } - }, 5000); + // Note: in response to SIGUSR1 we start drying up but do not exit when calls reach zero. + // This is to allow external scripts that sent the signal to manage the lifecycle. }); }