[jira] [Updated] (OAK-6626) Replace standby blob chunk size configuration with feature flag
[
https://issues.apache.org/jira/browse/OAK-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu updated OAK-6626:
-
Attachment: OAK-6626.patch
[~mduerig], could you please review the patch attached?
> Replace standby blob chunk size configuration with feature flag
> ---
>
> Key: OAK-6626
> URL: https://issues.apache.org/jira/browse/OAK-6626
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: cold-standby, configuration
> Fix For: 1.8, 1.7.11
>
> Attachments: OAK-6626.patch
>
>
> We should remove the {{StandbyStoreService#BLOB_CHUNK_SIZE}} OSGi
> configuration and replace it with a feature flag. Rational: we expect
> customer to rarely change this thus not justifying the additional
> configuration complexity and testing overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6747) improve path matching in RDBVersionGCSupport
[
https://issues.apache.org/jira/browse/OAK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6747:
Summary: improve path matching in RDBVersionGCSupport (was: improve patch
matching in RDBVersionGCSupport)
> improve path matching in RDBVersionGCSupport
>
>
> Key: OAK-6747
> URL: https://issues.apache.org/jira/browse/OAK-6747
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-6747.diff
>
>
> We currently find split documents by using "LIKE" to exclude regular
> documents. However, these "LIKE" expressions start with a wildcard, which
> defeats use of the index.
> We may be able to improve this by adding to the already existing exclusion
> patterns, such as:
> {noformat}
> 0:/% 1:/% 2:/% 3:/% 4:/% ...
> {noformat}
> We should benchmark this first, though. See OAK-6719.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5877) Oak upgrade usage note refers to oak-run
[
https://issues.apache.org/jira/browse/OAK-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5877:
--
Fix Version/s: (was: 1.7.10)
1.7.11
> Oak upgrade usage note refers to oak-run
>
>
> Key: OAK-5877
> URL: https://issues.apache.org/jira/browse/OAK-5877
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Michael Dürig
>Priority: Minor
> Labels: production, tooling, usability
> Fix For: 1.8, 1.7.11
>
>
> Running {{java -jar oak-upgrade*.jar}} prints
> {noformat}
> Usage: java -jar oak-run-*-jr2.jar upgrade [options] jcr2_source [destination]
>(to upgrade a JCR 2 repository)
>java -jar oak-run-*-jr2.jar upgrade [options] source destination
>(to migrate an Oak repository)
> {noformat}
> Which incorrectly refers to {{oak-run upgrade}}. The latter will send me back
> to {{oak-run}}: "This command was moved to the oak-upgrade module".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6762) Convert oak-blob to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6762: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-blob to OSGi R6 annotations > --- > > Key: OAK-6762 > URL: https://issues.apache.org/jira/browse/OAK-6762 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6756) Convert oak-auth-external to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6756: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-auth-external to OSGi R6 annotations > > > Key: OAK-6756 > URL: https://issues.apache.org/jira/browse/OAK-6756 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-external >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5763) Improve LockException message on org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
[
https://issues.apache.org/jira/browse/OAK-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5763:
--
Fix Version/s: (was: 1.7.10)
1.7.11
> Improve LockException message on
> org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
> --
>
> Key: OAK-5763
> URL: https://issues.apache.org/jira/browse/OAK-5763
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
>Affects Versions: 1.3.3
>Reporter: Borja Clemente
> Fix For: 1.8, 1.7.11
>
>
> The error message on LockManagerImpl unlock method could also include
> information about the user attempting to unlock the node as well as the
> actual lock owner.
> Current exception is:
> {code}
> LockException("Not an owner of the lock " + path)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6758) Convert oak-authorization-cug to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6758: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-authorization-cug to OSGi R6 annotations > > > Key: OAK-6758 > URL: https://issues.apache.org/jira/browse/OAK-6758 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: authorization-cug >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5976) Document enhancements in 1.6 release
[ https://issues.apache.org/jira/browse/OAK-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5976: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Document enhancements in 1.6 release > > > Key: OAK-5976 > URL: https://issues.apache.org/jira/browse/OAK-5976 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.11 > > > We should document all the enhancement that have been done in Oak 1.6 release > and refer to them in main doc > * 1.6.0 Release Notes - > https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.0/RELEASE-NOTES.txt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5455:
--
Fix Version/s: (was: 1.7.10)
1.7.11
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.11
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6764) Convert oak-exercise to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6764: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-exercise to OSGi R6 annotations > --- > > Key: OAK-6764 > URL: https://issues.apache.org/jira/browse/OAK-6764 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: exercise >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6759) Convert oak-blob-cloud-azure to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6759: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-blob-cloud-azure to OSGi R6 annotations > --- > > Key: OAK-6759 > URL: https://issues.apache.org/jira/browse/OAK-6759 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-cloud >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6769) Convert oak-search-mt to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6769: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-search-mt to OSGi R6 annotations > > > Key: OAK-6769 > URL: https://issues.apache.org/jira/browse/OAK-6769 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6760) Convert oak-blob-cloud to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6760: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-blob-cloud to OSGi R6 annotations > - > > Key: OAK-6760 > URL: https://issues.apache.org/jira/browse/OAK-6760 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-cloud >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5975) Document enhancements in Observation in 1.6
[ https://issues.apache.org/jira/browse/OAK-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5975: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Document enhancements in Observation in 1.6 > --- > > Key: OAK-5975 > URL: https://issues.apache.org/jira/browse/OAK-5975 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.11 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs wrt JCR Observation area > * OAK-4796 - filter events before adding to ChangeProcessor's queue > * OAK-5020 - Improved support for node removals > * OAK-5021 - Improve observation of files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6766) Convert oak-lucene to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6766: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-lucene to OSGi R6 annotations > - > > Key: OAK-6766 > URL: https://issues.apache.org/jira/browse/OAK-6766 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6774) Convert oak-upgrade to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6774: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-upgrade to OSGi R6 annotations > -- > > Key: OAK-6774 > URL: https://issues.apache.org/jira/browse/OAK-6774 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: upgrade >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5896) fix typo in Not condition handling
[ https://issues.apache.org/jira/browse/OAK-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5896: -- Fix Version/s: (was: 1.7.10) 1.7.11 > fix typo in Not condition handling > -- > > Key: OAK-5896 > URL: https://issues.apache.org/jira/browse/OAK-5896 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.6.1 >Reporter: Dave Brosius >Assignee: Dave Brosius >Priority: Trivial > Fix For: 1.8, 1.7.11 > > Attachments: 5896.txt > > > code stutters the same condition twice, looks like a typo. patch attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5918) Document enhancements in DocumentNodeStore in 1.6
[ https://issues.apache.org/jira/browse/OAK-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5918: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Document enhancements in DocumentNodeStore in 1.6 > - > > Key: OAK-5918 > URL: https://issues.apache.org/jira/browse/OAK-5918 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.11 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs. Specially those enhancements which impact > system administration or new features which need be to enabled as per > requirements should be documented > Issues in documentmk, mongomk, rdbmk > [jql|https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.6.0%20and%20component%20in%20(documentmk%2C%20mongomk%2C%20rdbmk)%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC&startIndex=200] > * OAK-1312 - Bundle nodes into a document (/) > * OAK-4180 - Use another NodeStore as a local cache for a remote Document > store (/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5998) Clarify and complete missing stuff in current Oak documentation
[ https://issues.apache.org/jira/browse/OAK-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5998: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Clarify and complete missing stuff in current Oak documentation > --- > > Key: OAK-5998 > URL: https://issues.apache.org/jira/browse/OAK-5998 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.11 > > > Current Oak documentation [1] is missing details around certain aspects of > Oak which makes it difficult for a new person to get up and running and more > important operate Oak in productions easily. Purpose of this task is list out > topic which must be documented to enable easier usage of Oak > * Getting Started - Getting Oak with all features properly is tricky and not > easily possible with our [current getting > started|https://jackrabbit.apache.org/oak/docs/construct.html] specially for > prod setup. > ** Possibly refer or move doc of current examples here > ** For a new user not aware of JCR but aware of document storage a brief > overview on the JCR and how its the api for Oak which is to be used > * Maintenance and Operations - > ** Oak being MVCC storage requires certain maintenance task like RevisionGC > and BlobGC to be run periodically. > ** Then related MBean should be documented. Note some part is covered in > [Segment > docs|https://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#garbage-collection] > but we need to complete it for Document and also provide an overview > ** System requirements in terms of RAM due to memory mapped usage, cloned > index files and persistent cache > * How clustering works in Oak - [Clustering > doc|https://jackrabbit.apache.org/oak/docs/clustering.html] should provide > details on > ** how it works > ** importance of background read and background write > ** Effect of eventual consistency in cluster setup > ** Sticky session requirement (as per usecase) > * Observation > ** How it works > ** How external and local events are generated > ** Queue behaviour and overflow > * Clarify requirement from host application wrt > ** scheduling singleton jobs used in Oak and how they should be executed > ** Scheduling maintenance operations via MBeans > * Document various OSGi config - May be generate a doc for all OSGi config in > Oak via some tooling > Note list above is tentative and would be edited to determine important > topics in coming days and then specific sub task can be created to complete > it. Once any list item is completed add (/) against the list entry > [1] https://jackrabbit.apache.org/oak/docs/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6768) Convert oak-remote to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6768: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-remote to OSGi R6 annotations > - > > Key: OAK-6768 > URL: https://issues.apache.org/jira/browse/OAK-6768 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: remoting >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5965) Support path exclusion in secondary nodestore
[ https://issues.apache.org/jira/browse/OAK-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5965: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Support path exclusion in secondary nodestore > - > > Key: OAK-5965 > URL: https://issues.apache.org/jira/browse/OAK-5965 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Labels: secondary-nodestore > Fix For: 1.8, 1.7.11 > > > Secondary NodeStore feature (OAK-4180) for now currently supports path > inclusion. It would be useful to have support for path exclusion also. > Using this a user can can include all content under / but exclude > /oak:index/uuid/:index entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5884) Evaluate utility of RepositoryGrowthTest benchmark
[
https://issues.apache.org/jira/browse/OAK-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5884:
--
Fix Version/s: (was: 1.7.10)
1.7.11
> Evaluate utility of RepositoryGrowthTest benchmark
> --
>
> Key: OAK-5884
> URL: https://issues.apache.org/jira/browse/OAK-5884
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: run
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> {{RepositoryGrowthTest}} is a benchmark which makes use of the deprecated
> {{SegmentFixture}}. Since OAK-5834 removes the old {{oak-segment}} module and
> the code associated with it, {{RepositoryGrowthTest}} was also removed. If
> there's value in it, we can adapt it to work with the new
> {{SegmentTarFixture}}.
> /cc [~chetanm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6741: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6761) Convert oak-blob-plugins to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6761: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-blob-plugins to OSGi R6 annotations > --- > > Key: OAK-6761 > URL: https://issues.apache.org/jira/browse/OAK-6761 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-plugins >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6767) Remove felix SCR annotation support from parent pom
[ https://issues.apache.org/jira/browse/OAK-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6767: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Remove felix SCR annotation support from parent pom > --- > > Key: OAK-6767 > URL: https://issues.apache.org/jira/browse/OAK-6767 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6773) Convert oak-store-composite to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6773: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-store-composite to OSGi R6 annotations > -- > > Key: OAK-6773 > URL: https://issues.apache.org/jira/browse/OAK-6773 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6757) Convert oak-auth-ldap to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6757: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-auth-ldap to OSGi R6 annotations > > > Key: OAK-6757 > URL: https://issues.apache.org/jira/browse/OAK-6757 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-ldap >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5963) Disable S3 proactive caching by default
[ https://issues.apache.org/jira/browse/OAK-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5963: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Disable S3 proactive caching by default > --- > > Key: OAK-5963 > URL: https://issues.apache.org/jira/browse/OAK-5963 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Labels: candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6 > Fix For: 1.8, 1.7.11 > > > The older JR2 CachingDataStore which is extended by S3DataStore enables > proactive caching by default which leads to many binaries being downloaded > twice. This should be disabled by default in Oak. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6765) Convert oak-jcr to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6765: -- Fix Version/s: (was: 1.7.10) 1.7.11 > Convert oak-jcr to OSGi R6 annotations > -- > > Key: OAK-6765 > URL: https://issues.apache.org/jira/browse/OAK-6765 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6747) improve patch matching in RDBVersionGCSupport
[
https://issues.apache.org/jira/browse/OAK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6747:
Summary: improve patch matching in RDBVersionGCSupport (was: improve index
handling in RDBVersionGCSupport)
> improve patch matching in RDBVersionGCSupport
> -
>
> Key: OAK-6747
> URL: https://issues.apache.org/jira/browse/OAK-6747
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-6747.diff
>
>
> We currently find split documents by using "LIKE" to exclude regular
> documents. However, these "LIKE" expressions start with a wildcard, which
> defeats use of the index.
> We may be able to improve this by adding to the already existing exclusion
> patterns, such as:
> {noformat}
> 0:/% 1:/% 2:/% 3:/% 4:/% ...
> {noformat}
> We should benchmark this first, though. See OAK-6719.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6747) improve index handling in RDBVersionGCSupport
[
https://issues.apache.org/jira/browse/OAK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-6747.
-
Resolution: Later
Ran VersionGCTest with scale=1000 for three DBs, twice, with and without the
change.
trunk:
{noformat}
DB2: 2.149 min
DB2: 2.179 min
Oracle: 1.328 min
Oracle: 1.846 min
PostgreSQL: 1.627 min
PostgreSQL: 1.391 min
{noformat}
with patch:
{noformat}
DB2: 2.042 min
DB2: 1.928 min
Oracle: 1.887 min
Oracle: 1.501 min
PostgreSQL: 1.824 min
PostgreSQL: 1.848 min
{noformat}
Needs more research.
> improve index handling in RDBVersionGCSupport
> -
>
> Key: OAK-6747
> URL: https://issues.apache.org/jira/browse/OAK-6747
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: OAK-6747.diff
>
>
> We currently find split documents by using "LIKE" to exclude regular
> documents. However, these "LIKE" expressions start with a wildcard, which
> defeats use of the index.
> We may be able to improve this by adding to the already existing exclusion
> patterns, such as:
> {noformat}
> 0:/% 1:/% 2:/% 3:/% 4:/% ...
> {noformat}
> We should benchmark this first, though. See OAK-6719.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6859) Enable continuous revision GC on MongoDB
Marcel Reutegger created OAK-6859: - Summary: Enable continuous revision GC on MongoDB Key: OAK-6859 URL: https://issues.apache.org/jira/browse/OAK-6859 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk, mongomk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Fix For: 1.8 Continuous Revision GC for DocumentNodeStore on MongoDB should be enabled by default. This avoids the need to trigger the GC externally and also avoids high load on the system when it run e.g. once a day. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6770: --- Fix Version/s: (was: 1.7.11) > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6770: --- Priority: Minor (was: Major) > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6773) Convert oak-store-composite to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215059#comment-16215059 ] Robert Munteanu commented on OAK-6773: -- Unable to work on this in the next couple of weeks → unassigning > Convert oak-store-composite to OSGi R6 annotations > -- > > Key: OAK-6773 > URL: https://issues.apache.org/jira/browse/OAK-6773 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215058#comment-16215058 ] Robert Munteanu commented on OAK-6770: -- This is purely a technical task, enabling Oak to take advantage of recent enhancement in the annotations, most visible one being the annotation-based component configuration. There is no requirement to finish it for 1.8, as migrating just parts of Oak works fine. > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6773) Convert oak-store-composite to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned OAK-6773: Assignee: (was: Robert Munteanu) > Convert oak-store-composite to OSGi R6 annotations > -- > > Key: OAK-6773 > URL: https://issues.apache.org/jira/browse/OAK-6773 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215052#comment-16215052 ] Michael Dürig commented on OAK-6770: [~rombert], could you clarify the requirements and priorities of this re. the 1.8 release? > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6858) Log revision sweep progress on startup
Marcel Reutegger created OAK-6858: - Summary: Log revision sweep progress on startup Key: OAK-6858 URL: https://issues.apache.org/jira/browse/OAK-6858 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Priority: Minor Fix For: 1.8 The DocumentNodeStore should log progress of the revision sweep operation when it runs on startup. This is a one-time operation that is triggered when Oak is upgraded to 1.8 or newer. Ideally, the revision sweep is done with oak-run as part of a coordinated cluster upgrade as documented here: https://jackrabbit.apache.org/oak/docs/nodestore/document/upgrade.html For cases where the sweep is not performed with oak-run, the implementation should write log messages why startup takes longer than usual and also provide progress messages. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6855) Researching Build Breakage
[ https://issues.apache.org/jira/browse/OAK-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-6855. --- Resolution: Not A Problem > Researching Build Breakage > -- > > Key: OAK-6855 > URL: https://issues.apache.org/jira/browse/OAK-6855 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Dereck >Priority: Minor > > Dear developers of the jackrabbit-oak project, > We are MSc students from the Delft University of Technology doing research on > why builds break in open source projects. To do this, we are analyzing Travis > build statistics and build history of jackrabbit-oak. > By analyzing the build history of jackrabbit-oak, we found the following: > * The project has 45% failing builds in the history > * The project has a high amount of build failures compared to other similar > projects > When looking at jackrabbit-oak’s build metrics, we could not find clear > factors that are highly correlated with this result. > To identify the reasons behind build breakage, we would like to collect > developer insights into the reasons why build breakage occurs. If you have > five minutes, please answer the > [survey|https://www.surveymonkey.com/r/PQ7XTGM] we have created. Your > response will be very useful in our study. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6813) DocumentStore conditional remove: reduce set of supported conditions to what the Version GC needs
[ https://issues.apache.org/jira/browse/OAK-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215009#comment-16215009 ] Marcel Reutegger commented on OAK-6813: --- I like the simplified proposal better. It limits the functionality to what is really needed and nothing more. This not only simplifies the contract, but also the implementations and tests. [~chetanm], [~catholicon], WDYT? > DocumentStore conditional remove: reduce set of supported conditions to what > the Version GC needs > - > > Key: OAK-6813 > URL: https://issues.apache.org/jira/browse/OAK-6813 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.8 > > Attachments: OAK-6813.diff > > > ...and verify in tests that implementations consistently reject other > variants. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6857) Lucene unique index should check path validity for uniqueness constraint
Chetan Mehrotra created OAK-6857:
Summary: Lucene unique index should check path validity for
uniqueness constraint
Key: OAK-6857
URL: https://issues.apache.org/jira/browse/OAK-6857
Project: Jackrabbit Oak
Issue Type: Technical task
Components: lucene
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Fix For: 1.8
The {{UniquenessConstraintValidator}} currently checks for any new index entry
if any matching entry is found in primary (property) and secondary (lucene)
index.
This can lead to false positive where the entry in index is obsolete and due to
async index lagging behind is yet not pruned. For e.g. if
# Time T1 - path /a/@uuid=1 existed , present in lucene index
# Time T2 - path /a removed (async index yet not catched up)
# Time T3 - path /b/@uuid=1 being created.
In this case save should pass. However as async index has yet not catched up it
reports a constraint validation exception. As a fix
{{UniquenessConstraintValidator}} should check if reported paths are valid wrt
current revision
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6856) DocumentNodeStore upgrade to 1.8 when RDB access is only possible through application server
[ https://issues.apache.org/jira/browse/OAK-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6856: Issue Type: Improvement (was: Bug) > DocumentNodeStore upgrade to 1.8 when RDB access is only possible through > application server > > > Key: OAK-6856 > URL: https://issues.apache.org/jira/browse/OAK-6856 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke > > https://jackrabbit.apache.org/oak/docs/nodestore/document/upgrade.html > currently assumes that the admin has access to the persistence from within > oak-run. This might not be true for the RDB persistence when Oak runs in an > application server and the DataSource is obtained through JNDI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6856) DocumentNodeStore upgrade to 1.8 when RDB access is only possible through application server
Julian Reschke created OAK-6856: --- Summary: DocumentNodeStore upgrade to 1.8 when RDB access is only possible through application server Key: OAK-6856 URL: https://issues.apache.org/jira/browse/OAK-6856 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk Reporter: Julian Reschke https://jackrabbit.apache.org/oak/docs/nodestore/document/upgrade.html currently assumes that the admin has access to the persistence from within oak-run. This might not be true for the RDB persistence when Oak runs in an application server and the DataSource is obtained through JNDI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6813) DocumentStore conditional remove: reduce set of supported conditions to what the Version GC needs
[
https://issues.apache.org/jira/browse/OAK-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214935#comment-16214935
]
Julian Reschke commented on OAK-6813:
-
A simplified API proposal:
Change:
{noformat}
int remove(Collection collection,
Map> toRemove)
throws DocumentStoreException;
{noformat}
to
{noformat}
int remove(Collection collection,
List> toRemove)
throws DocumentStoreException;
{noformat}
...where the list would contain pairs of Document IDs and MODIFIED values (to
be checked with "equals")
> DocumentStore conditional remove: reduce set of supported conditions to what
> the Version GC needs
> -
>
> Key: OAK-6813
> URL: https://issues.apache.org/jira/browse/OAK-6813
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 1.8
>
> Attachments: OAK-6813.diff
>
>
> ...and verify in tests that implementations consistently reject other
> variants.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-3878) Avoid caching of NodeDocument while iterating in BlobReferenceIterator
[
https://issues.apache.org/jira/browse/OAK-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214814#comment-16214814
]
Marcel Reutegger commented on OAK-3878:
---
bq. isn't it actually a bit dangerous to bypass the cache in these cases?
What do you mean with 'these cases'? Is this about the signature change
proposed earlier by Chetan? That is, adding a {{cacheResults}} parameter. If
yes, then the contract should be clear about what the impact is on subsequent
calls that may return cached documents. My preference is also to invalidate
cached documents if the implementation determines the cached document is
outdated. This ensures all changes visible in the non-cached result are also
visible in a subsequent potentially cached result.
On the other hand, if this is about the current BlobReferenceIterator
implementations ({{RDBBlobReferenceIterator}} and
{{MongoBlobReferenceIterator}}), then I think reading the documents should be
an implementation detail because the BlobReferenceIterator itself only returns
{{ReferencedBlob}} instances and not documents. The consistency guarantees of
the BlobReferenceIterator (currently not specified) may be slightly different
from the DocumentStore API.
> Avoid caching of NodeDocument while iterating in BlobReferenceIterator
> --
>
> Key: OAK-3878
> URL: https://issues.apache.org/jira/browse/OAK-3878
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.8
>
>
> {{BlobReferenceIterator}} in DocumentMK makes use of {{DocumentStore}} API to
> query the NodeDocument. This would cause all those NodeDocuments to be added
> to cache in DocumentStore. Due to this when blob gc is running cache usage
> would not be that effective due to all the associated churn.
> As these NodeDocument are only required for BlobGC logic and its not expected
> that this document would read again soon it would be better to skip caching
> of these documents within DocumentStore
> Similar requirement exist in VersionGC logic but there we use direct store
> based API which does not add such documents to the cache
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6855) Researching Build Breakage
Dereck created OAK-6855: --- Summary: Researching Build Breakage Key: OAK-6855 URL: https://issues.apache.org/jira/browse/OAK-6855 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Dereck Priority: Minor Dear developers of the jackrabbit-oak project, We are MSc students from the Delft University of Technology doing research on why builds break in open source projects. To do this, we are analyzing Travis build statistics and build history of jackrabbit-oak. By analyzing the build history of jackrabbit-oak, we found the following: * The project has 45% failing builds in the history * The project has a high amount of build failures compared to other similar projects When looking at jackrabbit-oak’s build metrics, we could not find clear factors that are highly correlated with this result. To identify the reasons behind build breakage, we would like to collect developer insights into the reasons why build breakage occurs. If you have five minutes, please answer the [survey|https://www.surveymonkey.com/r/PQ7XTGM] we have created. Your response will be very useful in our study. Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6854) Update Oak trunk to Jackrabbit 2.16.0
[ https://issues.apache.org/jira/browse/OAK-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6854: Issue Type: Task (was: Bug) > Update Oak trunk to Jackrabbit 2.16.0 > - > > Key: OAK-6854 > URL: https://issues.apache.org/jira/browse/OAK-6854 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6854) Update Oak trunk to Jackrabbit 2.16.0
Julian Reschke created OAK-6854: --- Summary: Update Oak trunk to Jackrabbit 2.16.0 Key: OAK-6854 URL: https://issues.apache.org/jira/browse/OAK-6854 Project: Jackrabbit Oak Issue Type: Bug Components: parent Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5860) Compressed segments
[ https://issues.apache.org/jira/browse/OAK-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5860: --- Fix Version/s: (was: 1.8) > Compressed segments > --- > > Key: OAK-5860 > URL: https://issues.apache.org/jira/browse/OAK-5860 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segment-tar >Reporter: Michael Dürig >Assignee: Andrei Dulceanu > Labels: scalability > > It would be interesting to see the effect of compressing the segments within > the tar files with a sufficiently effective and performant compression > algorithm: > * Can we increase overall throughput by trading CPU for IO? > * Can we scale to bigger repositories (in number of nodes) by squeezing in > more segments per MB and thus pushing out onset of thrashing? > * What would be a good compression algorithm/library? > * Can/should we make this optional? > * Migration and compatibility issues? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6584) Add tooling API
[ https://issues.apache.org/jira/browse/OAK-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6584: --- Fix Version/s: 1.7.12 > Add tooling API > --- > > Key: OAK-6584 > URL: https://issues.apache.org/jira/browse/OAK-6584 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segment-tar >Reporter: Michael Dürig >Assignee: Michael Dürig > Labels: tooling > Fix For: 1.8, 1.7.12 > > > h3. Current situation > Current segment store related tools are implemented ad-hoc by potentially > relying on internal implementation details of Oak Segment Tar. This makes > those tools less useful, portable, stable and potentially applicable than > they should be. > h3. Goal > Provide a common and sufficiently stable Oak Tooling API for implementing > segment store related tools. The API should be independent of Oak and not > available for normal production use of Oak. Specifically it should not be > possible to it to implement production features and production features must > not rely on it. It must be possible to implement the Oak Tooling API in Oak > 1.8 and it should be possible for Oak 1.6. > h3. Typical use cases > * Query the number of nodes / properties / values in a given path satisfying > some criteria > * Aggregate a certain value on queries like the above > * Calculate size of the content / size on disk > * Analyse changes. E.g. how many binaries bigger than a certain threshold > were added / removed between two given revisions. What is the sum of their > sizes? > * Analyse locality: measure of locality of node states. Incident plots (See > https://issues.apache.org/jira/browse/OAK-5655?focusedCommentId=15865973&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15865973). > * Analyse level of deduplication (e.g. of checkpoint) > h3. Validation > Reimplement [Script Oak|https://github.com/mduerig/script-oak] on top of the > tooling API. > h3. API draft > * Whiteboard shot of the [API > entities|https://wiki.apache.org/jackrabbit/Oakathon%20August%202017?action=AttachFile&do=view&target=IMG_20170822_163256.jpg] > identified initially. > * Further [drafting of the API|https://github.com/mduerig/oak-tooling-api] > takes place on Github for now. We'll move to the Apache SVN as soon as > considered mature enough and have a consensus of where to best move it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5360) Cancellation of gc should be reflected by RevisionGC.getRevisionGCStatus()
[
https://issues.apache.org/jira/browse/OAK-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5360:
---
Fix Version/s: (was: 1.7.10)
1.7.11
> Cancellation of gc should be reflected by RevisionGC.getRevisionGCStatus()
> --
>
> Key: OAK-5360
> URL: https://issues.apache.org/jira/browse/OAK-5360
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: gc, management, monitoring, production
> Fix For: 1.8, 1.7.11
>
>
> Currently when a garbage collection cycle is cancelled from "within" (i.e.
> through {{CancelCompactionSupplier}} then this is not reflected through
> {{RevisionGC.getRevisionGCStatus()}} but rather reported as successful run.
> We should change this and return a failure result indication the cancellation
> so downstream consumers get an proper indication whether and which gc runs
> actually succeeded.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6626) Replace standby blob chunk size configuration with feature flag
[
https://issues.apache.org/jira/browse/OAK-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6626:
---
Fix Version/s: (was: 1.7.10)
1.7.11
> Replace standby blob chunk size configuration with feature flag
> ---
>
> Key: OAK-6626
> URL: https://issues.apache.org/jira/browse/OAK-6626
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: cold-standby, configuration
> Fix For: 1.8, 1.7.11
>
>
> We should remove the {{StandbyStoreService#BLOB_CHUNK_SIZE}} OSGi
> configuration and replace it with a feature flag. Rational: we expect
> customer to rarely change this thus not justifying the additional
> configuration complexity and testing overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6627) Backup restore should interact properly with older segment version
[ https://issues.apache.org/jira/browse/OAK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6627: --- Fix Version/s: (was: 1.7.10) 1.7.11 > Backup restore should interact properly with older segment version > -- > > Key: OAK-6627 > URL: https://issues.apache.org/jira/browse/OAK-6627 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Michael Dürig >Assignee: Michael Dürig > Labels: production, resilience > Fix For: 1.8, 1.7.11 > > > We need to check how backup and restore behave when run on top of a former > store version. That is backup / restore from Oak 1.8 to / from stores of > segment version 12 (from Oak 1.6). Expected behaviour is "nothing bad > happens". Details to be clarified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6674) Create a more complex IT for cold standby
[
https://issues.apache.org/jira/browse/OAK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6674:
---
Fix Version/s: (was: 1.7.10)
1.7.11
> Create a more complex IT for cold standby
> -
>
> Key: OAK-6674
> URL: https://issues.apache.org/jira/browse/OAK-6674
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.8, 1.7.11
>
>
> At the moment all integration tests for cold standby are using the same
> scenario in their tests: some content is created on the server (including
> binaries), a standby sync cycle is started and then the content is checked on
> the client. The only twist here is using/not using a data store for storing
> binaries.
> Although good, this model could be extended to cover many more cases. For
> example, {{StandbyDiff}} covers the following 6 cases node/property
> added/changed/deleted. From these, with the scenario described, the removal
> part is never tested (and the change part is covered in only one test).
> It would be nice to have an IT which would add content on the server, do a
> sync, remove some of the content, do a sync and then call OnRC. This way all
> cases will be covered, including if cleanup works as expected on the client.
> /cc [~frm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6606) Move BulkTransferBenchmark to oak-benchmarks module
[
https://issues.apache.org/jira/browse/OAK-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6606:
---
Fix Version/s: (was: 1.7.10)
1.7.11
> Move BulkTransferBenchmark to oak-benchmarks module
> ---
>
> Key: OAK-6606
> URL: https://issues.apache.org/jira/browse/OAK-6606
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.11
>
>
> {{BulkTransferBenchmark}} should be moved from {{oak-segment-tar}} to
> {{oak-benchmarks}} to allow standard run of this cold standby related
> benchmark.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6737) Standby server should send timely responses to all client requests
[
https://issues.apache.org/jira/browse/OAK-6737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6737:
---
Fix Version/s: (was: 1.7.10)
1.7.11
> Standby server should send timely responses to all client requests
> --
>
> Key: OAK-6737
> URL: https://issues.apache.org/jira/browse/OAK-6737
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.11
>
>
> Currently all the {{GetXXXRequestHandler}} (where XXX stands for Blob, Head,
> References and Segment), on the server discard client requests which cannot
> be satisfied (i.e. the requested object does not exist (yet) on the server).
> A more transparent approach would be to timely respond to all client
> requests, clearly stating that the object was not found. This would improve a
> lot debugging for example, because all requests and their responses could be
> easily followed from the client log, without needing to know what actually
> happened on the server.
> Below, a possible implementation for {{GetHeadRequestHandler}}, suggested by
> [~frm] in a comment on OAK-6678:
> {noformat}
> String id = reader.readHeadRecordId();
> if (id == null) {
> ctx.writeAndFlush(new NotFoundGetHeadResponse(msg.getClientId(), id));
> return;
> }
> ctx.writeAndFlush(new GetHeadResponse(msg.getClientId(), id));
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5635) Revisit FileStoreStats mbean stats format
[ https://issues.apache.org/jira/browse/OAK-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5635: --- Fix Version/s: (was: 1.7.10) 1.7.11 > Revisit FileStoreStats mbean stats format > - > > Key: OAK-5635 > URL: https://issues.apache.org/jira/browse/OAK-5635 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Alex Deparvu >Assignee: Michael Dürig > Labels: monitoring > Fix For: 1.8, 1.7.11 > > > This is a bigger refactoring item to revisit the format of the exposed data, > moving towards having it in a more machine consumable friendly format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
