Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30551

Add a configurable TTL to control how long a blob remains in the storage after async key generation

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.10-HF42
    • Fix Version/s: 10.10-HF53, 2021.9
    • Component/s: BlobManager, S3
    • Release Notes Summary:
      It is possible to configure how long a blob is kept after a new key has been computed for it.
    • Release Notes Description:
      Hide

      After async blob digest computation a blob's key is changed to its digest by creating a new blob and deleting the old one. The old one is deleted after a delay which can be configured through:

        <require>org.nuxeo.ecm.core.blob.BlobManager</require>
        <extension target="org.nuxeo.runtime.ConfigurationService" point="configuration">
          <property name="nuxeo.blobmanager.delete.delay">2h</property>
        </extension>
      

      The default is one hour.

      Show
      After async blob digest computation a blob's key is changed to its digest by creating a new blob and deleting the old one. The old one is deleted after a delay which can be configured through: <require> org.nuxeo.ecm.core.blob.BlobManager </require> <extension target= "org.nuxeo.runtime.ConfigurationService" point= "configuration" > <property name= "nuxeo.blobmanager.delete.delay" > 2h </property> </extension> The default is one hour.
    • Tags:
    • Backlog priority:
      850
    • Team:
      FG

      Description

      As described in NXP-30044, once the asynchronous computation of the digest is finished, the original blob is removed.

      It could be a problem if a process is started as soon as the original blob is saved to the final S3 storage.

      This ticket is to control with a TTL parameter how long the binary will remain in the storage before being removed by the async digest computation.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day
                1d

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.