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

Property index stored locally

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • None
    • 1.6.0
    • documentmk, query
    • None

    Description

      When running Oak in a cluster, each write operation is expensive. After performing some stress-tests with a geo-distributed Mongo cluster, we've found out that updating property indexes is a large part of the overall traffic. Let's try to create a new property-local index, that will save the indexed data locally, without sharing it.

      Assumptions:
      -there's a new property-local index type for which the data are saved in the local SegmentNodeStore instance created specifically for this purpose,
      -local changes are indexed using a new editor, based on the PropertyIndexEditor,
      -remote changes are extracted from the JournalEntries fetched in the background read operation and indexed as well,
      -the new index type won't support uniqueness restriction.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            tomek.rekawek Tomek Rękawek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment