[jira] [Resolved] (OAK-7363) Build Jackrabbit Oak #1328 failed

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu resolved OAK-7363.
---
Resolution: Duplicate

> Build Jackrabbit Oak #1328 failed
> -
>
> Key: OAK-7363
> URL: https://issues.apache.org/jira/browse/OAK-7363
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1328 has failed.
> First failed run: [Jackrabbit Oak 
> #1328|https://builds.apache.org/job/Jackrabbit%20Oak/1328/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1328/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu reopened OAK-7355:
---

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7363) Build Jackrabbit Oak #1328 failed

[Hudson (JIRA)]

Hudson created OAK-7363:
---

 Summary: Build Jackrabbit Oak #1328 failed
 Key: OAK-7363
 URL: https://issues.apache.org/jira/browse/OAK-7363
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit Oak #1328 has failed.
First failed run: [Jackrabbit Oak 
#1328|https://builds.apache.org/job/Jackrabbit%20Oak/1328/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1328/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7356) CugConfiguration may not pick up CugExclude

[angela (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406543#comment-16406543
 ] 

angela commented on OAK-7356:
-

[~stillalex] thanks a bunch! I will rework the patch accordingly...

> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not 
> properly pick up the {{CugExclude}}, which results in the 
> {{CugConfiguration}} falling back to the default, that only excludes the 
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG 
> evaluation.
> In order to address the issue without disrupting the default setup, I would 
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the 
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to 
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop 
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from 
> {{CugExclude.Default}} the default behavior in absense of a configured set of 
> principal names will be equivalent to the intended default in 
> {{CugConfiguration}} with the optional reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7356) CugConfiguration may not pick up CugExclude

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406528#comment-16406528
 ] 

Alex Deparvu commented on OAK-7356:
---

a bit of feedback:
* {{CugConfiguration}} I'm ok with setting reference to required, it enforces 
the expectations, but I think it creates a bit of confusion with the detault 
being injected in. is that for tests only? also the log statements are a bit 
confusing, it seems you are logging OSGi wiring behavior not sure how useful 
this is long term  
 * {{CugExcludeImpl}} I'm ok with setting {{immediate}} to true. a bit 
uncertain about the {{principalNames}}. it seems they can be empty? (if I start 
without a dedicated config for example). also there must be a better way of 
exposing the value other than debug logs, OSGi has something that allows for 
the status to be exported but I need to dig up a reference (ideally I would be 
able to see the value on a running system without restart/debug).
 

> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not 
> properly pick up the {{CugExclude}}, which results in the 
> {{CugConfiguration}} falling back to the default, that only excludes the 
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG 
> evaluation.
> In order to address the issue without disrupting the default setup, I would 
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the 
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to 
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop 
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from 
> {{CugExclude.Default}} the default behavior in absense of a configured set of 
> principal names will be equivalent to the intended default in 
> {{CugConfiguration}} with the optional reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[JIRA]

[ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406512#comment-16406512
 ] 

Michael Dürig commented on OAK-7355:


[~tomek.rekawek], I think there is a rat Maven profile you could run locally to 
verify.

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7358) Remove all usage of java.security.acl.Group for Java 11

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406507#comment-16406507
 ] 

Alex Deparvu commented on OAK-7358:
---

patch 
https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:oak-7024-no-group

> Remove all usage of java.security.acl.Group for Java 11
> ---
>
> Key: OAK-7358
> URL: https://issues.apache.org/jira/browse/OAK-7358
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.9.0
>
>
> Followup of OAK-7024 for the actual removal of the Group class from the 
> codebase to be java 11 compliant.
> Not sure what to use for 'fix version', I went with 1.9.0 so this remains on 
> the radar, but we can push it out as needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406466#comment-16406466
 ] 

Alex Deparvu commented on OAK-7355:
---

hehe, still some left

{noformat}
[WARNING] Files with unapproved licenses:
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-azure/src/test/java/org/apache/jackrabbit/oak/segment/azure/AzureManifestFileTest.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-azure/src/test/java/org/apache/jackrabbit/oak/segment/azure/AzureGCJournalTest.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-azure/start-azurite.sh
{noformat}

I didn't know about the extra ones, I just copy/pasted the jenkins build output 
:)


> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7362) Build Jackrabbit Oak #1326 failed

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu resolved OAK-7362.
---
Resolution: Duplicate

> Build Jackrabbit Oak #1326 failed
> -
>
> Key: OAK-7362
> URL: https://issues.apache.org/jira/browse/OAK-7362
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1326 has failed.
> First failed run: [Jackrabbit Oak 
> #1326|https://builds.apache.org/job/Jackrabbit%20Oak/1326/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1326/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7362) Build Jackrabbit Oak #1326 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406389#comment-16406389
 ] 

Hudson commented on OAK-7362:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1327|https://builds.apache.org/job/Jackrabbit%20Oak/1327/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1327/console]

> Build Jackrabbit Oak #1326 failed
> -
>
> Key: OAK-7362
> URL: https://issues.apache.org/jira/browse/OAK-7362
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1326 has failed.
> First failed run: [Jackrabbit Oak 
> #1326|https://builds.apache.org/job/Jackrabbit%20Oak/1326/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1326/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7362) Build Jackrabbit Oak #1326 failed

[Hudson (JIRA)]

Hudson created OAK-7362:
---

 Summary: Build Jackrabbit Oak #1326 failed
 Key: OAK-7362
 URL: https://issues.apache.org/jira/browse/OAK-7362
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit Oak #1326 has failed.
First failed run: [Jackrabbit Oak 
#1326|https://builds.apache.org/job/Jackrabbit%20Oak/1326/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1326/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek resolved OAK-7355.

Resolution: Fixed

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[JIRA]

[ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406326#comment-16406326
 ] 

Tomek Rękawek commented on OAK-7355:


Thanks [~stillalex] - fixed in [r1827308|https://svn.apache.org/r1827308].

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-6976) CopyOnWriteDirectory_Segment_Test failure

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-6976:

Fix Version/s: (was: 1.0.42)
   1.0.43

> CopyOnWriteDirectory_Segment_Test failure
> -
>
> Key: OAK-6976
> URL: https://issues.apache.org/jira/browse/OAK-6976
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: lucene
>Affects Versions: 1.4.18
>Reporter: Marcel Reutegger
>Assignee: Chetan Mehrotra
>Priority: Major
> Fix For: 1.4.21, 1.2.30, 1.0.43
>
>
> This test only exists in branches 1.4 and older and was introduced as part of 
> OAK-5238. The test fails every now and then with (stack trace from 1.4):
> {noformat}
> java.lang.IllegalStateException: This builder does not exist: child-0
>   at 
> com.google.common.base.Preconditions.checkState(Preconditions.java:150)
>   at 
> org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:506)
>   at 
> org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:515)
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.CopyOnWriteDirectory_Segment_Test.writeTree(CopyOnWriteDirectory_Segment_Test.java:158)
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.CopyOnWriteDirectory_Segment_Test.copyOnWrite(CopyOnWriteDirectory_Segment_Test.java:111)
> {noformat}
> Please note that it fails more likely when the update.limit is set to 100, 
> which is the case for the maven build.
> I also ported the test to 1.6 and running it with the new segment-tar looks 
> OK. I don't know if this is because the copy-on-write or the segment-tar 
> implementation is different than in 1.4. 
> The affected versions are currently only set to 1.4.18, because there were no 
> releases off the 1.2 and 1.0 branches since OAK-5238 was backported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5609) Test failure: org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5609:

Fix Version/s: 1.0.43

> Test failure: 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers
> -
>
> Key: OAK-5609
> URL: https://issues.apache.org/jira/browse/OAK-5609
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, core
>Affects Versions: 1.0.36
>Reporter: Hudson
>Priority: Major
>  Labels: test-failure, windows
> Fix For: 1.0.43
>
> Attachments: unit-tests-1454.log, unit-tests.log
>
>
> Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/
> The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 
> 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #443 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #443|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/443/]
>  [console 
> log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/443/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5609) Test failure: org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5609:

Fix Version/s: (was: 1.0.42)

> Test failure: 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers
> -
>
> Key: OAK-5609
> URL: https://issues.apache.org/jira/browse/OAK-5609
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, core
>Affects Versions: 1.0.36
>Reporter: Hudson
>Priority: Major
>  Labels: test-failure, windows
> Fix For: 1.0.43
>
> Attachments: unit-tests-1454.log, unit-tests.log
>
>
> Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/
> The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 
> 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #443 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #443|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/443/]
>  [console 
> log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/443/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5534) Build timed out

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5534:

Fix Version/s: (was: 1.0.42)
   1.0.43

> Build timed out
> ---
>
> Key: OAK-5534
> URL: https://issues.apache.org/jira/browse/OAK-5534
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>  Labels: CI, test-failure, ubuntu
> Fix For: 1.0.43
>
> Attachments: console-1432-document-rdb.txt, console-1432-segment.txt, 
> console.txt
>
>
> Jenkins CI failure: 
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting 
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5532) Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5532:

Fix Version/s: (was: 1.0.42)
   1.0.43

> Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...
> -
>
> Key: OAK-5532
> URL: https://issues.apache.org/jira/browse/OAK-5532
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, segmentmk
>Reporter: Hudson
>Priority: Major
>  Labels: test-failure, ubuntu
> Fix For: 1.0.43
>
> Attachments: build1401-unit-tests.log, unit-tests.log
>
>
> Jenkins CI failure: 
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
> (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting 
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1384/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1384/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5264) Test failure: SolrIndexHookIT.testPropertyAddition

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5264:

Fix Version/s: (was: 1.0.42)
   1.0.43

> Test failure: SolrIndexHookIT.testPropertyAddition
> --
>
> Key: OAK-5264
> URL: https://issues.apache.org/jira/browse/OAK-5264
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Affects Versions: 1.0.35, 1.2.22, 1.5.15
>Reporter: Hudson
>Assignee: Tommaso Teofili
>Priority: Major
>  Labels: test-failure, ubuntu
> Fix For: 1.0.43
>
>
> Jenkins CI failure: 
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5404) Test failure: SolrIndexQueryTestIT.testNativeMLTQuery and testNativeMLTQueryWithStream

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5404:

Fix Version/s: (was: 1.0.42)
   1.0.43

> Test failure:  SolrIndexQueryTestIT.testNativeMLTQuery and 
> testNativeMLTQueryWithStream
> ---
>
> Key: OAK-5404
> URL: https://issues.apache.org/jira/browse/OAK-5404
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Affects Versions: 1.0
>Reporter: Thomas Mueller
>Assignee: Tommaso Teofili
>Priority: Major
>  Labels: test-failure, ubuntu
> Fix For: 1.0.43
>
>
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.jackrabbit.oak.plugins.index.solr.query.SolrIndexQueryTestIT.testNativeMLTQueryWithStream(SolrIndexQueryTestIT.java:286)
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.jackrabbit.oak.plugins.index.solr.query.SolrIndexQueryTestIT.testNativeMLTQuery(SolrIndexQueryTestIT.java:264)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu reopened OAK-7355:
---

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7361) Build Jackrabbit Oak #1325 failed

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu resolved OAK-7361.
---
Resolution: Duplicate

> Build Jackrabbit Oak #1325 failed
> -
>
> Key: OAK-7361
> URL: https://issues.apache.org/jira/browse/OAK-7361
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1325 has failed.
> First failed run: [Jackrabbit Oak 
> #1325|https://builds.apache.org/job/Jackrabbit%20Oak/1325/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1325/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406286#comment-16406286
 ] 

Alex Deparvu commented on OAK-7355:
---

Missing licence headers:
{noformat}
[WARNING] Files with unapproved licenses:
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/GCJournalFile.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/JournalFile.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/RepositoryLock.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/JournalFileWriter.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/JournalFileReader.java
  /home/jenkins/jenkins-slave/workspace/Jackrabbit 
Oak/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/ManifestFile.java
{noformat}

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7361) Build Jackrabbit Oak #1325 failed

[Hudson (JIRA)]

Hudson created OAK-7361:
---

 Summary: Build Jackrabbit Oak #1325 failed
 Key: OAK-7361
 URL: https://issues.apache.org/jira/browse/OAK-7361
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit Oak #1325 has failed.
First failed run: [Jackrabbit Oak 
#1325|https://builds.apache.org/job/Jackrabbit%20Oak/1325/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1325/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu resolved OAK-6956.
---
Resolution: Fixed
  Assignee: Alex Deparvu  (was: Tomek Rękawek)

fixed with http://svn.apache.org/viewvc?rev=1827304&view=rev

> RepositoryUpgrade hardcodes SecurityProvider
> 
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: angela
>Assignee: Alex Deparvu
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6956.patch
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) 
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} 
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use 
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7360) Migrate to the MongoDB Java driver API 3.0

[Marcel Reutegger (JIRA)]

Marcel Reutegger created OAK-7360:
-

 Summary: Migrate to the MongoDB Java driver API 3.0
 Key: OAK-7360
 URL: https://issues.apache.org/jira/browse/OAK-7360
 Project: Jackrabbit Oak
  Issue Type: Technical task
  Components: mongomk
Reporter: Marcel Reutegger
 Fix For: 1.10


The {{MongoDocumentStore}} currently uses the old API in {{com.mongodb}}. 
Starting with MongoDB Java driver 3.0 a new client API was introduced in 
{{com.mongodb.client}}. New features like client sessions are only available in 
the new API and MongoDB may remove some deprecated methods/classes/interfaces 
in the future. The implementation should be migrated to the new client API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7359) Update to MongoDB Java driver 3.6

[Marcel Reutegger (JIRA)]

Marcel Reutegger created OAK-7359:
-

 Summary: Update to MongoDB Java driver 3.6
 Key: OAK-7359
 URL: https://issues.apache.org/jira/browse/OAK-7359
 Project: Jackrabbit Oak
  Issue Type: Technical task
  Components: mongomk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
 Fix For: 1.10


Update the MongoDB Java driver to 3.6 to make use of new features when running 
on a MongoDB 3.6.x server.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5607) Test failure: security.authentication.ldap.LdapProviderTest.testGetUnknownUserByRef

[Manfred Baedke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-5607:

Fix Version/s: (was: 1.0.42)
   1.0.43

> Test failure: 
> security.authentication.ldap.LdapProviderTest.testGetUnknownUserByRef
> ---
>
> Key: OAK-5607
> URL: https://issues.apache.org/jira/browse/OAK-5607
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-ldap, continuous integration
>Affects Versions: 1.0.36, 1.6.0
>Reporter: Hudson
>Assignee: Manfred Baedke
>Priority: Major
>  Labels: test-failure, windows
> Fix For: 1.0.43
>
> Attachments: unit-tests.log
>
>
> Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/
> The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 
> 64-bit Windows only,nsfixtures=SEGMENT_MK,profile=unittesting #441 has failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
> security) 64-bit Windows only,nsfixtures=SEGMENT_MK,profile=unittesting 
> #441|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=unittesting/441/]
>  [console 
> log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=unittesting/441/console]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7339) Fix all sidegrades breaking with UnsupportedOperationException on MissingBlobStore by introducing LoopbackBlobStore

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek updated OAK-7339:
---
Labels: candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6 
candidate_oak_1_8  (was: candidate_oak_1_6 candidate_oak_1_8)

> Fix all sidegrades breaking with UnsupportedOperationException on 
> MissingBlobStore by introducing LoopbackBlobStore
> ---
>
> Key: OAK-7339
> URL: https://issues.apache.org/jira/browse/OAK-7339
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Affects Versions: 1.6.0, 1.8.0
>Reporter: Arek Kita
>Assignee: Tomek Rękawek
>Priority: Major
>  Labels: candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6, 
> candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7339-jenkins-xml-encoding-issue.patch, OAK-7339.patch
>
>
> h4. Problem
> In some edge cases when the binary under the same path (/content/asset1) is 
> modified by 2 independent checkpoints: A & B the sidegrade without providing 
> DataStore might fail with the following error:
> {noformat:title=An exception thrown by oak-upgrade tool}
> Caused by: java.lang.UnsupportedOperationException: null
>     at 
> org.apache.jackrabbit.oak.upgrade.cli.blob.MissingBlobStore.getInputStream(MissingBlobStore.java:62)
>     at 
> org.apache.jackrabbit.oak.plugins.blob.BlobStoreBlob.getNewStream(BlobStoreBlob.java:47)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentBlob.getNewStream(SegmentBlob.java:276)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentBlob.getNewStream(SegmentBlob.java:86)
>     at 
> org.apache.jackrabbit.oak.plugins.memory.AbstractBlob$1.openStream(AbstractBlob.java:44)
>     at com.google.common.io.ByteSource.contentEquals(ByteSource.java:344)
>     at 
> org.apache.jackrabbit.oak.plugins.memory.AbstractBlob.equal(AbstractBlob.java:67)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentBlob.equals(SegmentBlob.java:227)
>     at com.google.common.base.Objects.equal(Objects.java:60)
>     at 
> org.apache.jackrabbit.oak.plugins.memory.AbstractPropertyState.equal(AbstractPropertyState.java:59)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentPropertyState.equals(SegmentPropertyState.java:242)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareProperties(SegmentNodeState.java:617)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:511)
> (the same nested methods)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:604)
>     at 
> org.apache.jackrabbit.oak.upgrade.PersistingDiff.diff(PersistingDiff.java:139)
>     at 
> org.apache.jackrabbit.oak.upgrade.PersistingDiff.childNodeChanged(PersistingDiff.java:191)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.MapRecord$3.childNodeChanged(MapRecord.java:440)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.MapRecord.compare(MapRecord.java:483)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.MapRecord.compare(MapRecord.java:432)
>     at 
> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:604)
>     at 
> org.apache.jackrabbit.oak.upgrade.PersistingDiff.diff(PersistingDiff.java:139)
>     at 
> org.apache.jackrabbit.oak.upgrade.PersistingDiff.applyDiffOnNodeState(PersistingDiff.java:106)
>     at 
> org.apache.jackrabbit.oak.upgrade.RepositorySidegrade.copyDiffToTarget(RepositorySidegrade.java:403)
>     at 
> org.apache.jackrabbit.oak.upgrade.RepositorySidegrade.migrateWithCheckpoints(RepositorySidegrade.java:347)
> {noformat}
>  
> h4. Abstract of proposed solution
> The idea for migration is simple: instead of failing on:
> {code:java}
> public InputStream getInputStream(String blobId) throws IOException;
> {code}
> or
> {code:java}
> public int readBlob(String blobId, long pos, byte[] buff, int off, int 
> length) throws IOException;
> {code}
> lets introduce a BlobStore implementation that acts similarly as a 
> *localhost* interface that what you sent it will resend back to this 
> interface.
> h4. How it works
> It works as a *localhost* interface, the same way: when *{{blobId}}* is 
> requested... then *{{blobId}}* is served as a binary content instead *of 
> throwing*: {{UnsupportedOperationException}}.
> This allows to act quickly on migrations that requires to compare binaries in 
> order to satisfy requirements for checkpoints to be rewritten, copied from 
> scratch.
> h4. Pros
>  * simplifies simple sidegrade migration use cases: you do not need anymore 
> to include your DataStore (which slows that migration not necessary) on the 
> 

[jira] [Commented] (OAK-7024) java.security.acl deprecated in Java 10, marked for removal in Java 11

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406185#comment-16406185
 ] 

Alex Deparvu commented on OAK-7024:
---

decided to rollback one small part of the patch with 
http://svn.apache.org/viewvc?rev=1827296&view=rev
initially I wanted to completely remove implementation of Group for the 
internal classes but it turned out that code that currently relies in 
instanceof checks can fail and this would be against the 'don't break anything' 
rule.
all removal of Group references will happen via OAK-7358 when the time comes.

> java.security.acl deprecated in Java 10, marked for removal in Java 11
> --
>
> Key: OAK-7024
> URL: https://issues.apache.org/jira/browse/OAK-7024
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: security
>Reporter: Julian Reschke
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> See  and 
> .
> Need to understand how this affects public Oak APIs, and what to do with them 
> on Java 11 (which will be an LTS release we probably need to support with Oak 
> 1.10).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-7297) New fixture for the Azure Segment Store

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek reassigned OAK-7297:
--

Assignee: Tomek Rękawek

> New fixture for the Azure Segment Store
> ---
>
> Key: OAK-7297
> URL: https://issues.apache.org/jira/browse/OAK-7297
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: benchmarks, it
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7297.patch
>
>
> We should add a new {{SEGMENT_AZURE}} fixture, so it's possible to run the 
> integrationt tests for the [Azure Segment Store|OAK-6922]. By default it 
> should connect to a local Azure Storage emulator:
> * https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator
> * https://github.com/arafato/azurite
> If the {{oak.segment.azure.connection}} system property is defined, then it 
> should try to connect to the specified [connection 
> string|https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek reassigned OAK-7355:
--

Assignee: Tomek Rękawek

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7297) New fixture for the Azure Segment Store

[JIRA]

[ 
https://issues.apache.org/jira/browse/OAK-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406126#comment-16406126
 ] 

Tomek Rękawek commented on OAK-7297:


Merged to trunk [r1827293|https://svn.apache.org/r1827293].

> New fixture for the Azure Segment Store
> ---
>
> Key: OAK-7297
> URL: https://issues.apache.org/jira/browse/OAK-7297
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: benchmarks, it
>Reporter: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7297.patch
>
>
> We should add a new {{SEGMENT_AZURE}} fixture, so it's possible to run the 
> integrationt tests for the [Azure Segment Store|OAK-6922]. By default it 
> should connect to a local Azure Storage emulator:
> * https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator
> * https://github.com/arafato/azurite
> If the {{oak.segment.azure.connection}} system property is defined, then it 
> should try to connect to the specified [connection 
> string|https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7297) New fixture for the Azure Segment Store

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek resolved OAK-7297.

Resolution: Fixed

> New fixture for the Azure Segment Store
> ---
>
> Key: OAK-7297
> URL: https://issues.apache.org/jira/browse/OAK-7297
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: benchmarks, it
>Reporter: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7297.patch
>
>
> We should add a new {{SEGMENT_AZURE}} fixture, so it's possible to run the 
> integrationt tests for the [Azure Segment Store|OAK-6922]. By default it 
> should connect to a local Azure Storage emulator:
> * https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator
> * https://github.com/arafato/azurite
> If the {{oak.segment.azure.connection}} system property is defined, then it 
> should try to connect to the specified [connection 
> string|https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-6922) Azure support for the segment-tar

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek resolved OAK-6922.

Resolution: Fixed

Merged to trunk in [r1827292|https://svn.apache.org/r1827292].

> Azure support for the segment-tar
> -
>
> Key: OAK-6922
> URL: https://issues.apache.org/jira/browse/OAK-6922
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6922-2.patch, OAK-6922-3.patch, OAK-6922.patch
>
>
> An Azure Blob Storage implementation of the segment storage, based on the 
> OAK-6921 work.
> h3. Segment files layout
> Thew new implementation doesn't use tar files. They are replaced with 
> directories, storing segments, named after their UUIDs. This approach has 
> following advantages:
> * no need to call seek(), which may be expensive on a remote file system. 
> Rather than that we can read the whole file (=segment) at once.
> * it's possible to send multiple segments at once, asynchronously, which 
> reduces the performance overhead (see below).
> The file structure is as follows:
> {noformat}
> [~]$ az storage blob list -c oak --output table
> Name  Blob Type
> Blob TierLengthContent Type  Last Modified
>   ---  
> ---      -
> oak/data0a.tar/.ca1326d1-edf4-4d53-aef0-0f14a6d05b63  BlockBlob   
>   192   application/octet-stream  2018-01-31T10:59:14+00:00
> oak/data0a.tar/0001.c6e03426-db9d-4315-a20a-12559e6aee54  BlockBlob   
>   262144application/octet-stream  2018-01-31T10:59:14+00:00
> oak/data0a.tar/0002.b3784e27-6d16-4f80-afc1-6f3703f6bdb9  BlockBlob   
>   262144application/octet-stream  2018-01-31T10:59:14+00:00
> oak/data0a.tar/0003.5d2f9588-0c92-4547-abf7-0263ee7c37bb  BlockBlob   
>   259216application/octet-stream  2018-01-31T10:59:14+00:00
> ...
> oak/data0a.tar/006e.7b8cf63d-849a-4120-aa7c-47c3dde25e48  BlockBlob   
>   4368  application/octet-stream  2018-01-31T12:01:09+00:00
> oak/data0a.tar/006f.93799ae9-288e-4b32-afc2-bbc676fad7e5  BlockBlob   
>   3792  application/octet-stream  2018-01-31T12:01:14+00:00
> oak/data0a.tar/0070.8b2d5ff2-6a74-4ac3-a3cc-cc439367c2aa  BlockBlob   
>   3680  application/octet-stream  2018-01-31T12:01:14+00:00
> oak/data0a.tar/0071.2a1c49f0-ce33-4777-a042-8aa8a704d202  BlockBlob   
>   7760  application/octet-stream  2018-01-31T12:10:54+00:00
> oak/journal.log.001   AppendBlob  
>   1010  application/octet-stream  2018-01-31T12:10:54+00:00
> oak/manifest  BlockBlob   
>   46application/octet-stream  2018-01-31T10:59:14+00:00
> oak/repo.lock BlockBlob   
> application/octet-stream  2018-01-31T10:59:14+00:00
> {noformat}
> For the segment files, each name is prefixed with the index number. This 
> allows to maintain an order, as in the tar archive. This order is normally 
> stored in the index files as well, but if it's missing, the recovery process 
> uses the prefixes to maintain it.
> Each file contains the raw segment data, with no padding/headers. Apart from 
> the segment files, there are 3 special files: binary references (.brf), 
> segment graph (.gph) and segment index (.idx).
> h3. Asynchronous writes
> Normally, all the TarWriter writes are synchronous, appending the segments to 
> the tar file. In case of Azure Blob Storage each write involves a network 
> latency. That's why the SegmentWriteQueue was introduced. The segments are 
> added to the blocking dequeue, which is served by a number of the consumer 
> threads, writing the segments to the cloud. There's also a map UUID->Segment, 
> which allows to return the segments in case they are requested by the 
> readSegment() method before they are actually persisted. Segments are removed 
> from the map only after a successful write operation.
> The flush() method blocks accepting the new segments and returns after all 
> waiting segments are written. The close() method waits until the current 
> operations are finished and stops all threads.
> The asynchronous mode can be disabled by setting the number of threads to 0.
> h5. Queue recovery mode
> If the Azure Blob Storage write() operation fails, the segment will be 
> re-added and the queue is switched to an "reco

[jira] [Resolved] (OAK-7355) Move the pluggable storage interfaces to the SPI package

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek resolved OAK-7355.

Resolution: Fixed

Merged to trunk in [r1827291|https://svn.apache.org/r1827291].

> Move the pluggable storage interfaces to the SPI package
> 
>
> Key: OAK-7355
> URL: https://issues.apache.org/jira/browse/OAK-7355
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: segment-tar
>Reporter: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7355.patch
>
>
> OAK-6921 introduces a new abstraction layer in the oak-segment-tar, which 
> allows to support storing the segments not only in the tar files, but in any 
> types of persistence, implementing the SegmentArchiveManager.
> The types required to implement a custom SegmentArchiveManager are now spread 
> across many places within the oak-segment-tar. This results in an extensive 
> export list in the OSGi bundle. In order to keep the SegmentNodeStore 
> implementation encapsulated, we should move the new interfaces and all the 
> other required classes into a new {{org.apache.jackrabbit.oak.segment.spi}} 
> package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

[JIRA]

[ 
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406120#comment-16406120
 ] 

Tomek Rękawek commented on OAK-6956:


Looks good to me too. Thanks for taking care of this!

> RepositoryUpgrade hardcodes SecurityProvider
> 
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: angela
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6956.patch
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) 
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} 
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use 
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

[angela (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406106#comment-16406106
 ] 

angela commented on OAK-6956:
-

[~stillalex], patch looks good to me.

> RepositoryUpgrade hardcodes SecurityProvider
> 
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: angela
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6956.patch
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) 
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} 
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use 
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406090#comment-16406090
 ] 

Alex Deparvu commented on OAK-6956:
---

proposed patch based on latest development of the security provider bits ( 
[^OAK-6956.patch] ). this removes the usage of the impl class, but doesn't not 
address one of the issues raised here: what happens to custom setups. If I 
understand correctly this revolves around the method that transforms old JR 
config into the new format based on config params ({{mapSecurityConfig}} 
method). if there's a custom case to be treated, I would expect the 
{{mapSecurityConfig}} method to evolve to fit the new case in and pass the 
correct settings to the security provider builder.

> RepositoryUpgrade hardcodes SecurityProvider
> 
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: angela
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6956.patch
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) 
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} 
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use 
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

[Alex Deparvu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Deparvu updated OAK-6956:
--
Attachment: OAK-6956.patch

> RepositoryUpgrade hardcodes SecurityProvider
> 
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: angela
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6956.patch
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) 
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} 
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use 
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7358) Remove all usage of java.security.acl.Group for Java 11

[Alex Deparvu (JIRA)]

Alex Deparvu created OAK-7358:
-

 Summary: Remove all usage of java.security.acl.Group for Java 11
 Key: OAK-7358
 URL: https://issues.apache.org/jira/browse/OAK-7358
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: security
Reporter: Alex Deparvu
Assignee: Alex Deparvu
 Fix For: 1.9.0


Followup of OAK-7024 for the actual removal of the Group class from the 
codebase to be java 11 compliant.
Not sure what to use for 'fix version', I went with 1.9.0 so this remains on 
the radar, but we can push it out as needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7354) Test failure ExternalIdentityImporterTest.importExternalUserWithPrincipalNames

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406061#comment-16406061
 ] 

Alex Deparvu commented on OAK-7354:
---

I still see this failing locally, so I further refactored the repo creation in 
the test http://svn.apache.org/viewvc?rev=1827287&view=rev

> Test failure ExternalIdentityImporterTest.importExternalUserWithPrincipalNames
> --
>
> Key: OAK-7354
> URL: https://issues.apache.org/jira/browse/OAK-7354
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-external, continuous integration
>Reporter: Hudson
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The build Jackrabbit Oak #1318 has failed.
> First failed run: [Jackrabbit Oak 
> #1318|https://builds.apache.org/job/Jackrabbit%20Oak/1318/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1318/console]
> {noformat}Test results:
> 2 tests failed.
> FAILED:  
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUserWithPrincipalNames
> Error Message:
> Node with the same UUID exists:/rep:security/rep:authorizables/rep:users/t: { 
> jcr:primaryType = rep:AuthorizableFolder, t7 = { ... }}
> Stack Trace:
> javax.jcr.ItemExistsException: Node with the same UUID 
> exists:/rep:security/rep:authorizables/rep:users/t: { jcr:primaryType = 
> rep:AuthorizableFolder, t7 = { ... }}
> at 
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.doImport(ExternalIdentityImporterTest.java:132)
> at 
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUserWithPrincipalNames(ExternalIdentityImporterTest.java:167)
> FAILED:  
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUser
> Error Message:
> Node with the same UUID exists:/rep:security/rep:authorizables/rep:users/t: { 
> jcr:primaryType = rep:AuthorizableFolder, tt = { ... }}
> Stack Trace:
> javax.jcr.ItemExistsException: Node with the same UUID 
> exists:/rep:security/rep:authorizables/rep:users/t: { jcr:primaryType = 
> rep:AuthorizableFolder, tt = { ... }}
> at 
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.doImport(ExternalIdentityImporterTest.java:132)
> at 
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUser(ExternalIdentityImporterTest.java:153)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6087) Avoid reads from MongoDB primary

[Marcel Reutegger (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406035#comment-16406035
 ] 

Marcel Reutegger commented on OAK-6087:
---

MongoDB 3.6 with causal consistency using client sessions requires some more 
work in Oak because support for client sessions was only added to the 
{{com.mongodb.client}} API introduced with 3.0. The MongoDocumentStore still 
uses the legacy API in {{com.mongodb}}. E.g. {{com.mongodb.DB}} vs 
{{com.mongodb.client.MongoDatabase}}.

> Avoid reads from MongoDB primary
> 
>
> Key: OAK-6087
> URL: https://issues.apache.org/jira/browse/OAK-6087
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: mongomk
>Reporter: Marcel Reutegger
>Priority: Major
>  Labels: scalability
>
> With OAK-2106 Oak now attempts to read from a MongoDB secondary when it 
> detects the requested data is available on the secondary.
> When multiple Oak cluster nodes are deployed on a MongoDB replica set, many 
> reads are still directed to the primary. One of the reasons why this is seen 
> in practice, are observers and JCR event listeners that are triggered rather 
> soon after a change happens and therefore read recently modified documents. 
> This makes it difficult for Oak to direct calls to a nearby secondary, 
> because changes may not yet be available there.
> A rather simple solution for the observers may be to delay processing of 
> changes until they are available on the near secondary.
> A more sophisticated solution discussed offline could hide the replica set 
> entirely and always read from the nearest secondary. Writes would obviously 
> still go to the primary, but only return when the write is available also on 
> the nearest secondary. This guarantees that any subsequent read is able to 
> see the preceding write.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-6087) Avoid reads from MongoDB primary

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger reassigned OAK-6087:
-

Assignee: Marcel Reutegger

> Avoid reads from MongoDB primary
> 
>
> Key: OAK-6087
> URL: https://issues.apache.org/jira/browse/OAK-6087
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: mongomk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Major
>  Labels: scalability
>
> With OAK-2106 Oak now attempts to read from a MongoDB secondary when it 
> detects the requested data is available on the secondary.
> When multiple Oak cluster nodes are deployed on a MongoDB replica set, many 
> reads are still directed to the primary. One of the reasons why this is seen 
> in practice, are observers and JCR event listeners that are triggered rather 
> soon after a change happens and therefore read recently modified documents. 
> This makes it difficult for Oak to direct calls to a nearby secondary, 
> because changes may not yet be available there.
> A rather simple solution for the observers may be to delay processing of 
> changes until they are available on the near secondary.
> A more sophisticated solution discussed offline could hide the replica set 
> entirely and always read from the nearest secondary. Writes would obviously 
> still go to the primary, but only return when the write is available also on 
> the nearest secondary. This guarantees that any subsequent read is able to 
> see the preceding write.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7337) CommitsTracker data is always empty when exposed via JMX

[Andrei Dulceanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulceanu resolved OAK-7337.
--
Resolution: Fixed

Thanks for reviewing, [~mduerig]! 
Fixed at r1827284.

> CommitsTracker data is always empty when exposed via JMX
> 
>
> Key: OAK-7337
> URL: https://issues.apache.org/jira/browse/OAK-7337
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
>  Labels: tooling
> Fix For: 1.9.0, 1.10
>
>
> Due to duplicate registration of {{SegmentNodeStoreStats}} in both 
> {{SegmentNodeStore}}  and {{LockBasedScheduler}}, we end up with two 
> instances of this MBean. The former gets exposed via JMX and always returns 
> empty tables for CommitsCountPerWriter and QueuedWriters, while the latter 
> correctly tracks these data, but is not exposed. To address this, we should 
> stick to only one instance of {{SegmentNodeStoreStats}}, used in both 
> {{SegmentNodeStore}} and {{LockBasedScheduler}}.
> While at this, two additional points to be addressed:
> # {{CommitsTracker}} needs to be unit tested
> # commits count map size needs to be configurable via 
> {{SegmentNodeStoreStats}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)