Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      This jira issue discusses the technical implications on the current design of Jackrabbit to introduce clustering.

      Particularly the following areas require thorough investigation:

      • SharedItemStateManager and its cache
      • cache integrity
      • cache design: look aside, write through?
      • hook for distributed cache, interface?
      • isolation level
      • transaction integrity within Jackrabbit, interaction with transient layer
      • VirtualItemStateProvider
      • same strategy as SharedItemStateManager?
      • Search index
      • single or per cluster node index?
      • Observation

      Please state more areas if needed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mreutegg Marcel Reutegger
              • Votes:
                7 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: