Commits on Sep 22, 2022

1. Reset allowed-no-matching-node-period timeout on new nodes in cluster …

   We allow for situation when there are no nodes in the cluster which
   match task requirement for timeout governed by
   node-scheduler.allowed-no-matching-node-period config variable.
   Previously if new node appeared in the cluster, but could not be used
   because it did not have enough free resources at given moment timeout
   counter was not reset.
   This commit changes the behaviour. If new node appears and then
   disappears again, the no-nodes timeout will be recounted again from
   zero.

   

   losipiuk committed Sep 22, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for 1e51671
   • Browse repository at this point

   Copy the full SHA

   1e51671 View commit details

   Browse the repository at this point in the history