You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I tried thinking about this a little more. Should we really not update the timestamp if there was nothing to process? I don't think that there is any harm in doing so but I don't yet understand the gain yet either.
Pros - Sounds "right"
Cons - Migrate gets triggered every minute so despite trying to batch uploads happened in last ...MIGRATE_INTERVAL we just batch uploads happen between last cron scheduling and current.
Environment info
Actual behavior
logs/timestamp.migrate
is updated even if the migration script is not calledExpected behavior
logs/timestamp.migrate
is updated only when the migration script is calledSteps to reproduce
More information - Screenshots / Logs / Other output
Here is the log of 2nd
manage_nsfs.js glacier migrate
The text was updated successfully, but these errors were encountered: