Hi Devs, While testing group scaling, I noticed when scaling down it takes 30 minutes from the moment scaling rule decides to terminate an instance.
An active member, which was selected by the rule, first moves to a "termination pending member map", and after a certain period (terminationPendingMemberExpiryTime) that member moves to an "obsolete member map". Then by the obsolete check rule, that member will be terminated via cloud controller. It seems because of the property terminationPendingMemberExpiryTime, default value of which is 30 minutes, this takes that amount of time to get terminated Sorry for asking, I might have missed some past discussions regarding this, could someone explain the purpose of moving the member to an intermediary map "termination pending member map", rather than moving directly to "obsolete member map"? Also, is terminationPendingMemberExpiryTime parameter configurable? (seems not) , and any reason for it to set to 30 minutes? Further, we should make sleep times of PendingMemberWatcher, ObsoletedMemberWatcher and TerminationPendingMemberWatcher configurable. WDYT? We need to document those configurable parameters as well, @Mari please note. Thanks, Sajith
