Bernd Mathiske created MESOS-2073:
-------------------------------------
Summary: Fetcher cache file verification, updating and invalidation
Key: MESOS-2073
URL: https://issues.apache.org/jira/browse/MESOS-2073
Project: Mesos
Issue Type: Improvement
Components: fetcher, slave
Reporter: Bernd Mathiske
Priority: Minor
The other tickets in the fetcher cache epic do not necessitate a check sum
(e.g. MD5, SHA*) for files cached by the fetcher. Whereas such a check sum
could be used to verify whether the file arrived without unintended
alterations, it can first and foremost be employed to detect and trigger
updates.
Scenario: If a UIR is requested for fetching and the indicated download has the
same check sum as the cached file, then the cache file will be used and the
download forgone. If the check sum is different, then fetching proceeds and the
cached file gets replaced.
This capability will be indicated by an additional field in the URI protobuf.
Details TBD, i.e. to be discussed in comments below.
In addition to the above, even if the check sum is the same, we can support
voluntary cache file invalidation: a fresh download can be requested, or the
caching behavior can be revoked entirely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
