Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-4440

Async upload in S3DataStore can lead to intermittent binary missing exception in cluster

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • blob
    • None

    Description

      S3DataStore supports async upload of binaries. This feature was added to speedup performance for cases where S3 is remote (i.e. Oak/JR2 app was running on premise) (JCR-3733)

      This feature would cause issue in cluster deployment where binaries get uploaded from any cluster node because its possible that binary is not uploaded to S3 (present in local cache of one of the cluster node) and some code in other cluster node tries to read the binary.

      This feature also poses problem in backup and restore where we would need backup the local S3 cache on all the cluster nodes

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. OAK-4903 Async uploads in S3 causes issues in a cluster

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Sub-task - The sub-task of the issue JCR-3733 Asynchronous upload file to S3

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              chetanm Chetan Mehrotra
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: