Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-4682

Decouple shadow repository actions from their master repositories

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      1

      Description

      Decouple shadow repository actions from their master repositories.

      Right now, every shadow repository maintains itself synchronously based on incoming content changes from master repository. This is bad, since the number of "attached" shadow repositories directly affects the performance of master repository (shadow activity is done as part of master repository activity, ie. if you deploy to a M2 repository that has M1 shadow, the M2 deploy processing time will contain the M1 processing time too).

      Since in above example, the creation (or deletion) of the symlink in M1 shadow repository does not have to occur immediately as M2 repository got deployed (removed) something, we should make shadows process master events asynchronously.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                velo Marvin Herman Froeder
                Reporter:
                cstamas Tamás Cservenák
                Last Updated By:
                Rich Seddon
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: