-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSFS: migration timestamp is updated unexpectedly #7856
Comments
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" WDYT @piste-jp-ibm @guymguym |
In my thought, it is good to update the timestamp in the case below.
I think this implementation might keep all files are started to migrate within 11 mins at most. |
This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed. |
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: