Node History Problem
Opened this issue · 0 comments
coin8086 commented
cyclecloud-scalelib/src/hpc/autoscale/node/nodehistory.py
Lines 154 to 161 in 4efda02
In SQLiteNodeHistory.update
, a new node (not in database yet) will be stored in datebase with a fresh last_match_time
, no matter the node.required
is true or not. Is it a problem? If an unrequired node can be saved with a fresh last_match_time
, then what does the last_match_time
really mean?