Uploaded image for project: 'CernVM'
  1. CernVM
  2. CVM-808

CVMFS S3-backend caching should be disabled for mutable objects

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: CernVM-FS 2.1.20
    • Fix Version/s: CernVM-FS 2.2.0
    • Component/s: CVMFS
    • Labels:
      None
    • Platforms:
      x86_64-slc6-gcc48-opt

      Description

      The Google cloud storage (in S3 compatibility mode) caches in default publicly readable objects [1], e.g. .cvmfswhitelist. This means that e.g. executing mkfs twice in same repository fails, because first created .cvmfswhitelist is always returned.

      The caching behaviour can be changed e.g. by adding "Cache-Control: no-cache" header [2] when uploading these mutable objects. For the immutable files it is probably best to keep the default caching behaviour, defined by each S3 cloud storage, and not to specify explicitly any cache directive. In practise new request type "s3fanout::JobInfo::kReqPutNoCache" (in addition to s3fanout::JobInfo::kReqPut) should be defined, which is used when uploading mutable objects.

      [1] https://cloud.google.com/storage/docs/concepts-techniques#bestpractices
      [2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9

        Attachments

          Activity

          Hide
          ssheikki Seppo Heikkila added a comment -

          This issue was fixed with pull request #838
          https://github.com/cvmfs/cvmfs/pull/838

          Show
          ssheikki Seppo Heikkila added a comment - This issue was fixed with pull request #838 https://github.com/cvmfs/cvmfs/pull/838
          Hide
          jblomer Jakob Blomer added a comment -

          Please don't close until released.

          Show
          jblomer Jakob Blomer added a comment - Please don't close until released.

            People

            • Assignee:
              ssheikki Seppo Heikkila
              Reporter:
              ssheikki Seppo Heikkila
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 4 hours
                4h
                Logged:
                Time Spent - Not Specified
                Not Specified