[ https://issues.apache.org/jira/browse/OAK-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252041#comment-15252041 ]
Tomek Rękawek commented on OAK-4233: ------------------------------------ OK, if everyone agrees that we should implement the Marcel's idea, let's do it. It'll help to solve the original issue anyway, as the index changes will be saved asynchronously. > Property index stored locally > ----------------------------- > > Key: OAK-4233 > URL: https://issues.apache.org/jira/browse/OAK-4233 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, query > Reporter: Tomek Rękawek > Priority: Minor > Fix For: 1.6 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)