vine: cache-invalid associated files must be removed · Issue #4134 · cooperative-computing-lab/cctools · GitHub
More Web Proxy on the site http://driver.im/
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
If a transfer fails with a cache-invalid message, it means the source worker is unable to fetch the file from the destination worker, indicating that the file has crashed on either the source or the destination.
To prevent future replication attempts or task executions from using this invalid file, we need to remove it from both the source and destination workers.
Otherwise, the manager may get stuck trying to use what it thinks are valid files.
Specifically, we should:
remove the replica from vine_file_replica_table
explicitly clean the file by sending a unlink message
Calling delete_worker_file seems appropriate
The text was updated successfully, but these errors were encountered:
Yes, I agree that aggressively unlinking files upon cache-invalid may conceal the root cause. However, just in my case, this fix is necessary to ensure the workflow can eventually complete when replica count is set to 10. Without it, the workflow always fails to finish with significant slowdowns.
Uh oh!
There was an error while loading. Please reload this page.
This is another reason causing workflow slowdown.
If a transfer fails with a
cache-invalid
message, it means the source worker is unable to fetch the file from the destination worker, indicating that the file has crashed on either the source or the destination.To prevent future replication attempts or task executions from using this invalid file, we need to remove it from both the source and destination workers.
Otherwise, the manager may get stuck trying to use what it thinks are valid files.
Specifically, we should:
vine_file_replica_table
unlink
messageCalling
delete_worker_file
seems appropriateThe text was updated successfully, but these errors were encountered: