[jira] [Resolved] (OAK-9993) Add utility method to remove unmerged branches
[ https://issues.apache.org/jira/browse/OAK-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9993. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged PR. > Add utility method to remove unmerged branches > -- > > Key: OAK-9993 > URL: https://issues.apache.org/jira/browse/OAK-9993 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.46.0 > > > Introduce a method that removes unmerged branch commits similar to > oak.removeCollisions() in oak-mongo.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9998) Build Jackrabbit/jackrabbit-oak-trunk #709 failed
[ https://issues.apache.org/jira/browse/OAK-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9998. - > Build Jackrabbit/jackrabbit-oak-trunk #709 failed > - > > Key: OAK-9998 > URL: https://issues.apache.org/jira/browse/OAK-9998 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #709 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #709|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/709/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/709/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9998) Build Jackrabbit/jackrabbit-oak-trunk #709 failed
[ https://issues.apache.org/jira/browse/OAK-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9998. --- Resolution: Duplicate > Build Jackrabbit/jackrabbit-oak-trunk #709 failed > - > > Key: OAK-9998 > URL: https://issues.apache.org/jira/browse/OAK-9998 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #709 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #709|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/709/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/709/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9993) Add utility method to remove unmerged branches
[ https://issues.apache.org/jira/browse/OAK-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634297#comment-17634297 ] Marcel Reutegger commented on OAK-9993: --- Created PR for review: https://github.com/apache/jackrabbit-oak/pull/753 > Add utility method to remove unmerged branches > -- > > Key: OAK-9993 > URL: https://issues.apache.org/jira/browse/OAK-9993 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > Introduce a method that removes unmerged branch commits similar to > oak.removeCollisions() in oak-mongo.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9997) Abort outdated build on push to PR branch
[ https://issues.apache.org/jira/browse/OAK-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634272#comment-17634272 ] Marcel Reutegger commented on OAK-9997: --- PR for review: https://github.com/apache/jackrabbit-oak/pull/755 > Abort outdated build on push to PR branch > - > > Key: OAK-9997 > URL: https://issues.apache.org/jira/browse/OAK-9997 > Project: Jackrabbit Oak > Issue Type: Task > Components: continuous integration >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > An ongoing build on Jenkins should be aborted when new commits are pushed to > a PR branch and a new build is triggered. > See also discussion on dev list: > https://lists.apache.org/thread/v2210h8fry5mwt5lbhhznbr63dcdfvrb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9997) Abort outdated build on push to PR branch
Marcel Reutegger created OAK-9997: - Summary: Abort outdated build on push to PR branch Key: OAK-9997 URL: https://issues.apache.org/jira/browse/OAK-9997 Project: Jackrabbit Oak Issue Type: Task Components: continuous integration Reporter: Marcel Reutegger Assignee: Marcel Reutegger An ongoing build on Jenkins should be aborted when new commits are pushed to a PR branch and a new build is triggered. See also discussion on dev list: https://lists.apache.org/thread/v2210h8fry5mwt5lbhhznbr63dcdfvrb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9993) Add utility method to remove unmerged branches
[ https://issues.apache.org/jira/browse/OAK-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9993: - Assignee: Marcel Reutegger > Add utility method to remove unmerged branches > -- > > Key: OAK-9993 > URL: https://issues.apache.org/jira/browse/OAK-9993 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > Introduce a method that removes unmerged branch commits similar to > oak.removeCollisions() in oak-mongo.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9992) Introduce limit for oak.removeCollisions()
[ https://issues.apache.org/jira/browse/OAK-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9992. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged PR. > Introduce limit for oak.removeCollisions() > -- > > Key: OAK-9992 > URL: https://issues.apache.org/jira/browse/OAK-9992 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.46.0 > > > Currently the utility method in oak.removeCollisions() attempts to remove all > collision markers for a given clusterId. With many collisions this can be a > rather expensive operation that is difficult to schedule for MongoDB. I've > seen cases where removing all collisions during DocumentNodeStore > initialization was blocked for a very long time on the update call to > MongoDB. On the MongoDB side the operation was retried many times because it > conflicted with other concurrent updates on the same document. > The method should have a third parameter that limits the number of collisions > to remove in one call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9992) Introduce limit for oak.removeCollisions()
[ https://issues.apache.org/jira/browse/OAK-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9992: -- Summary: Introduce limit for oak.removeCollisions() (was: ntroduce limit for oak.removeCollisions()) > Introduce limit for oak.removeCollisions() > -- > > Key: OAK-9992 > URL: https://issues.apache.org/jira/browse/OAK-9992 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > Currently the utility method in oak.removeCollisions() attempts to remove all > collision markers for a given clusterId. With many collisions this can be a > rather expensive operation that is difficult to schedule for MongoDB. I've > seen cases where removing all collisions during DocumentNodeStore > initialization was blocked for a very long time on the update call to > MongoDB. On the MongoDB side the operation was retried many times because it > conflicted with other concurrent updates on the same document. > The method should have a third parameter that limits the number of collisions > to remove in one call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9993) Add utility method to remove unmerged branches
Marcel Reutegger created OAK-9993: - Summary: Add utility method to remove unmerged branches Key: OAK-9993 URL: https://issues.apache.org/jira/browse/OAK-9993 Project: Jackrabbit Oak Issue Type: Improvement Components: run Reporter: Marcel Reutegger Introduce a method that removes unmerged branch commits similar to oak.removeCollisions() in oak-mongo.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9992) ntroduce limit for oak.removeCollisions()
Marcel Reutegger created OAK-9992: - Summary: ntroduce limit for oak.removeCollisions() Key: OAK-9992 URL: https://issues.apache.org/jira/browse/OAK-9992 Project: Jackrabbit Oak Issue Type: Improvement Components: run Reporter: Marcel Reutegger Assignee: Marcel Reutegger Currently the utility method in oak.removeCollisions() attempts to remove all collision markers for a given clusterId. With many collisions this can be a rather expensive operation that is difficult to schedule for MongoDB. I've seen cases where removing all collisions during DocumentNodeStore initialization was blocked for a very long time on the update call to MongoDB. On the MongoDB side the operation was retried many times because it conflicted with other concurrent updates on the same document. The method should have a third parameter that limits the number of collisions to remove in one call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9981) Add a option in purgecommand(oak-run) to skip purge operations on active base index
[ https://issues.apache.org/jira/browse/OAK-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17631732#comment-17631732 ] Marcel Reutegger commented on OAK-9981: --- [~mkataria], I think this causes OAK-9978. > Add a option in purgecommand(oak-run) to skip purge operations on active base > index > --- > > Key: OAK-9981 > URL: https://issues.apache.org/jira/browse/OAK-9981 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.46.0 > > > The index purge command should provide an option to not apply purge > operations on active base index. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9978) Test failure: PurgeOldIndexVersionTest. noDeleteIfInvalidIndexOperationVersion
[
https://issues.apache.org/jira/browse/OAK-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9978:
--
Summary: Test failure: PurgeOldIndexVersionTest.
noDeleteIfInvalidIndexOperationVersion (was: Build
Jackrabbit/jackrabbit-oak-trunk #689 failed)
> Test failure: PurgeOldIndexVersionTest. noDeleteIfInvalidIndexOperationVersion
> --
>
> Key: OAK-9978
> URL: https://issues.apache.org/jira/browse/OAK-9978
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #689 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #689|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/console]
> The initial build reported above timed out, but starting Nov 9th the
> following test fails in oak-run.
> {noformat}
> [ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 11.777 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest
> [ERROR]
> noDeleteIfInvalidIndexOperationVersion(org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest)
> Time elapsed: 0.761 s <<< FAILURE!
> java.lang.AssertionError:
> custom fooIndex don't have product version
> Expected: a string containing "IndexVersionOperation List is not valid for
> index"
> but: was "[The index '/oak:index/counter' isn't active, Cannot find any
> active index from the list: [/oak:index/counter base=/oak:index/counter
> product=0 custom=0], Not valid version operation list: '[/oak:index/counter
> base=/oak:index/counter product=0 custom=0]', skip all, The index
> '/oak:index/principalName' isn't active, Cannot find any active index from
> the list: [/oak:index/principalName base=/oak:index/principalName product=0
> custom=0], Not valid version operation list: '[/oak:index/principalName
> base=/oak:index/principalName product=0 custom=0]', skip all, The index
> '/oak:index/uuid' isn't active, Cannot find any active index from the list:
> [/oak:index/uuid base=/oak:index/uuid product=0 custom=0], Not valid version
> operation list: '[/oak:index/uuid base=/oak:index/uuid product=0 custom=0]',
> skip all, The index '/oak:index/authorizableId' isn't active, Cannot find any
> active index from the list: [/oak:index/authorizableId
> base=/oak:index/authorizableId product=0 custom=0], Not valid version
> operation list: '[/oak:index/authorizableId base=/oak:index/authorizableId
> product=0 custom=0]', skip all, The index '/oak:index/acPrincipalName' isn't
> active, Cannot find any active index from the list:
> [/oak:index/acPrincipalName base=/oak:index/acPrincipalName product=0
> custom=0], Not valid version operation list: '[/oak:index/acPrincipalName
> base=/oak:index/acPrincipalName product=0 custom=0]', skip all, The index
> '/oak:index/reference' isn't active, Cannot find any active index from the
> list: [/oak:index/reference base=/oak:index/reference product=0 custom=0],
> Not valid version operation list: '[/oak:index/reference
> base=/oak:index/reference product=0 custom=0]', skip all, Found active index
> '/oak:index/fooIndex-4-custom-2', Found active index
> /oak:index/fooIndex-4-custom-2 is old enough, The operation for index
> '/oak:index/fooIndex-4-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3-custom-2' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-2-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex' will be: 'DELETE', The index '/oak:index/nodetype'
> isn't active, Cannot find any active index from the list:
> [/oak:index/nodetype base=/oak:index/nodetype product=0 custom=0], Not valid
> version operation list: '[/oak:index/nodetype base=/oak:index/nodetype
> product=0 custom=0]', skip all, The index '/oak:index/repMembers' isn't
> active, Cannot find any active index from the list: [/oak:index/repMembers
> base=/oak:index/repMembers product=0 custom=0], Not valid version operation
> list: '[/oak:index/repMembers base=/oak:index/repMembers product=0
> custom=0]', skip all]"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9978) Test failure: PurgeOldIndexVersionTest. noDeleteIfInvalidIndexOperationVersion
[
https://issues.apache.org/jira/browse/OAK-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9978:
--
Component/s: run
> Test failure: PurgeOldIndexVersionTest. noDeleteIfInvalidIndexOperationVersion
> --
>
> Key: OAK-9978
> URL: https://issues.apache.org/jira/browse/OAK-9978
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, run
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #689 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #689|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/console]
> The initial build reported above timed out, but starting Nov 9th the
> following test fails in oak-run.
> {noformat}
> [ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 11.777 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest
> [ERROR]
> noDeleteIfInvalidIndexOperationVersion(org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest)
> Time elapsed: 0.761 s <<< FAILURE!
> java.lang.AssertionError:
> custom fooIndex don't have product version
> Expected: a string containing "IndexVersionOperation List is not valid for
> index"
> but: was "[The index '/oak:index/counter' isn't active, Cannot find any
> active index from the list: [/oak:index/counter base=/oak:index/counter
> product=0 custom=0], Not valid version operation list: '[/oak:index/counter
> base=/oak:index/counter product=0 custom=0]', skip all, The index
> '/oak:index/principalName' isn't active, Cannot find any active index from
> the list: [/oak:index/principalName base=/oak:index/principalName product=0
> custom=0], Not valid version operation list: '[/oak:index/principalName
> base=/oak:index/principalName product=0 custom=0]', skip all, The index
> '/oak:index/uuid' isn't active, Cannot find any active index from the list:
> [/oak:index/uuid base=/oak:index/uuid product=0 custom=0], Not valid version
> operation list: '[/oak:index/uuid base=/oak:index/uuid product=0 custom=0]',
> skip all, The index '/oak:index/authorizableId' isn't active, Cannot find any
> active index from the list: [/oak:index/authorizableId
> base=/oak:index/authorizableId product=0 custom=0], Not valid version
> operation list: '[/oak:index/authorizableId base=/oak:index/authorizableId
> product=0 custom=0]', skip all, The index '/oak:index/acPrincipalName' isn't
> active, Cannot find any active index from the list:
> [/oak:index/acPrincipalName base=/oak:index/acPrincipalName product=0
> custom=0], Not valid version operation list: '[/oak:index/acPrincipalName
> base=/oak:index/acPrincipalName product=0 custom=0]', skip all, The index
> '/oak:index/reference' isn't active, Cannot find any active index from the
> list: [/oak:index/reference base=/oak:index/reference product=0 custom=0],
> Not valid version operation list: '[/oak:index/reference
> base=/oak:index/reference product=0 custom=0]', skip all, Found active index
> '/oak:index/fooIndex-4-custom-2', Found active index
> /oak:index/fooIndex-4-custom-2 is old enough, The operation for index
> '/oak:index/fooIndex-4-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3-custom-2' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-3' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex-2-custom-1' will be: 'DELETE', The operation for index
> '/oak:index/fooIndex' will be: 'DELETE', The index '/oak:index/nodetype'
> isn't active, Cannot find any active index from the list:
> [/oak:index/nodetype base=/oak:index/nodetype product=0 custom=0], Not valid
> version operation list: '[/oak:index/nodetype base=/oak:index/nodetype
> product=0 custom=0]', skip all, The index '/oak:index/repMembers' isn't
> active, Cannot find any active index from the list: [/oak:index/repMembers
> base=/oak:index/repMembers product=0 custom=0], Not valid version operation
> list: '[/oak:index/repMembers base=/oak:index/repMembers product=0
> custom=0]', skip all]"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9978) Build Jackrabbit/jackrabbit-oak-trunk #689 failed
[
https://issues.apache.org/jira/browse/OAK-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9978:
--
Description:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #689 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#689|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/console]
The initial build reported above timed out, but starting Nov 9th the following
test fails in oak-run.
{noformat}
[ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.777
s <<< FAILURE! - in
org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest
[ERROR]
noDeleteIfInvalidIndexOperationVersion(org.apache.jackrabbit.oak.indexversion.PurgeOldIndexVersionTest)
Time elapsed: 0.761 s <<< FAILURE!
java.lang.AssertionError:
custom fooIndex don't have product version
Expected: a string containing "IndexVersionOperation List is not valid for
index"
but: was "[The index '/oak:index/counter' isn't active, Cannot find any
active index from the list: [/oak:index/counter base=/oak:index/counter
product=0 custom=0], Not valid version operation list: '[/oak:index/counter
base=/oak:index/counter product=0 custom=0]', skip all, The index
'/oak:index/principalName' isn't active, Cannot find any active index from the
list: [/oak:index/principalName base=/oak:index/principalName product=0
custom=0], Not valid version operation list: '[/oak:index/principalName
base=/oak:index/principalName product=0 custom=0]', skip all, The index
'/oak:index/uuid' isn't active, Cannot find any active index from the list:
[/oak:index/uuid base=/oak:index/uuid product=0 custom=0], Not valid version
operation list: '[/oak:index/uuid base=/oak:index/uuid product=0 custom=0]',
skip all, The index '/oak:index/authorizableId' isn't active, Cannot find any
active index from the list: [/oak:index/authorizableId
base=/oak:index/authorizableId product=0 custom=0], Not valid version operation
list: '[/oak:index/authorizableId base=/oak:index/authorizableId product=0
custom=0]', skip all, The index '/oak:index/acPrincipalName' isn't active,
Cannot find any active index from the list: [/oak:index/acPrincipalName
base=/oak:index/acPrincipalName product=0 custom=0], Not valid version
operation list: '[/oak:index/acPrincipalName base=/oak:index/acPrincipalName
product=0 custom=0]', skip all, The index '/oak:index/reference' isn't active,
Cannot find any active index from the list: [/oak:index/reference
base=/oak:index/reference product=0 custom=0], Not valid version operation
list: '[/oak:index/reference base=/oak:index/reference product=0 custom=0]',
skip all, Found active index '/oak:index/fooIndex-4-custom-2', Found active
index /oak:index/fooIndex-4-custom-2 is old enough, The operation for index
'/oak:index/fooIndex-4-custom-1' will be: 'DELETE', The operation for index
'/oak:index/fooIndex-3-custom-2' will be: 'DELETE', The operation for index
'/oak:index/fooIndex-3-custom-1' will be: 'DELETE', The operation for index
'/oak:index/fooIndex-3' will be: 'DELETE', The operation for index
'/oak:index/fooIndex-2-custom-1' will be: 'DELETE', The operation for index
'/oak:index/fooIndex' will be: 'DELETE', The index '/oak:index/nodetype' isn't
active, Cannot find any active index from the list: [/oak:index/nodetype
base=/oak:index/nodetype product=0 custom=0], Not valid version operation list:
'[/oak:index/nodetype base=/oak:index/nodetype product=0 custom=0]', skip all,
The index '/oak:index/repMembers' isn't active, Cannot find any active index
from the list: [/oak:index/repMembers base=/oak:index/repMembers product=0
custom=0], Not valid version operation list: '[/oak:index/repMembers
base=/oak:index/repMembers product=0 custom=0]', skip all]"
{noformat}
was:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #689 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#689|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/console]
> Build Jackrabbit/jackrabbit-oak-trunk #689 failed
> -
>
> Key: OAK-9978
> URL: https://issues.apache.org/jira/browse/OAK-9978
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #689 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #689|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/689/]
> [console
>
[jira] [Resolved] (OAK-9967) Lease update duration not displayed correctly if timed-out
[ https://issues.apache.org/jira/browse/OAK-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9967. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged the PR into trunk. > Lease update duration not displayed correctly if timed-out > -- > > Key: OAK-9967 > URL: https://issues.apache.org/jira/browse/OAK-9967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Rishabh Kumar >Priority: Minor > Fix For: 1.46.0 > > > Stats for Lease update duration are not collected when it timed out. This > would be useful in determining the reason for pod restart/termination. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9967) Lease update duration not displayed correctly if timed-out
[ https://issues.apache.org/jira/browse/OAK-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9967: -- Priority: Minor (was: Major) > Lease update duration not displayed correctly if timed-out > -- > > Key: OAK-9967 > URL: https://issues.apache.org/jira/browse/OAK-9967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Rishabh Kumar >Priority: Minor > > Stats for Lease update duration are not collected when it timed out. This > would be useful in determining the reason for pod restart/termination. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9971) Migrate Oak maintenance builds from Travis CI to Jenkins
Marcel Reutegger created OAK-9971: - Summary: Migrate Oak maintenance builds from Travis CI to Jenkins Key: OAK-9971 URL: https://issues.apache.org/jira/browse/OAK-9971 Project: Jackrabbit Oak Issue Type: Task Components: continuous integration Reporter: Marcel Reutegger Oak maintenance branches currently build on Travis CI, which will no longer be supported by end of 2022. See: https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations Oak trunk already moved away from Travis CI to Apache operated Jenkins. The easiest solution is probably to merge changes from OAK-9486 into Oak maintenance branches that are still supported (1.22 and 1.8). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9925) update MongoDB Java Driver dependency to 3.12.11
[ https://issues.apache.org/jira/browse/OAK-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9925: -- Fix Version/s: 1.22.13 Labels: (was: candidate_oak_1_22) Merged into 1.22 branch with PR #730. > update MongoDB Java Driver dependency to 3.12.11 > > > Key: OAK-9925 > URL: https://issues.apache.org/jira/browse/OAK-9925 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.46.0, 1.22.13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9961) Build Jackrabbit/jackrabbit-oak-trunk #653 failed
[ https://issues.apache.org/jira/browse/OAK-9961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9961. --- Resolution: Fixed > Build Jackrabbit/jackrabbit-oak-trunk #653 failed > - > > Key: OAK-9961 > URL: https://issues.apache.org/jira/browse/OAK-9961 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #653 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #653|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/653/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/653/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9961) Build Jackrabbit/jackrabbit-oak-trunk #653 failed
[
https://issues.apache.org/jira/browse/OAK-9961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615571#comment-17615571
]
Marcel Reutegger commented on OAK-9961:
---
{noformat}
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from
https://github.com/apache/jackrabbit-oak
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1002)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1243)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1307)
at hudson.scm.SCM.checkout(SCM.java:540)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1215)
at
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:645)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517)
at hudson.model.Run.execute(Run.java:1896)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
--progress -- https://github.com/apache/jackrabbit-oak
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: error: Could not read 129e126ccb48d0128809d5c76e4b9ef57a8bf4fd
error: Could not read a802edfb11f078978ac9051406b740c24f7ab841
error: Could not read 468ca85a5b9b8bc2396c75c8154424bce7353870
{noformat}
Temporarily instructed the job to clean the workspace before executing. Looks
like that helped...
> Build Jackrabbit/jackrabbit-oak-trunk #653 failed
> -
>
> Key: OAK-9961
> URL: https://issues.apache.org/jira/browse/OAK-9961
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #653 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #653|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/653/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/653/console]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-9925) update MongoDB Java Driver dependency to 3.12.11
[ https://issues.apache.org/jira/browse/OAK-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615158#comment-17615158 ] Marcel Reutegger edited comment on OAK-9925 at 10/10/22 3:19 PM: - bq. backport this one to 1.22 +1 agreed. PR for 1.22 backport: https://github.com/apache/jackrabbit-oak/pull/730 was (Author: mreutegg): bq. backport this one to 1.22 +1 agreed. > update MongoDB Java Driver dependency to 3.12.11 > > > Key: OAK-9925 > URL: https://issues.apache.org/jira/browse/OAK-9925 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.46.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9925) update MongoDB Java Driver dependency to 3.12.11
[ https://issues.apache.org/jira/browse/OAK-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615158#comment-17615158 ] Marcel Reutegger commented on OAK-9925: --- bq. backport this one to 1.22 +1 agreed. > update MongoDB Java Driver dependency to 3.12.11 > > > Key: OAK-9925 > URL: https://issues.apache.org/jira/browse/OAK-9925 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.46.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9913) Expose Metrics for Mongo DocumentStore throttling
[ https://issues.apache.org/jira/browse/OAK-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9913. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged the PR. > Expose Metrics for Mongo DocumentStore throttling > - > > Key: OAK-9913 > URL: https://issues.apache.org/jira/browse/OAK-9913 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Rishabh Kumar >Assignee: Marcel Reutegger >Priority: Major > Fix For: 1.46.0 > > > Expose metrics for the Mongo DocumentStore throttling feature. This allows us > to better observe when the DocumentStore is throttled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9913) Expose Metrics for Mongo DocumentStore throttling
[ https://issues.apache.org/jira/browse/OAK-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9913: - Assignee: Marcel Reutegger > Expose Metrics for Mongo DocumentStore throttling > - > > Key: OAK-9913 > URL: https://issues.apache.org/jira/browse/OAK-9913 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Rishabh Kumar >Assignee: Marcel Reutegger >Priority: Major > > Expose metrics for the Mongo DocumentStore throttling feature. This allows us > to better observe when the DocumentStore is throttled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9891) Removal (purge) of version of a node does not remove associated labels
[
https://issues.apache.org/jira/browse/OAK-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9891:
--
Fix Version/s: 1.22.13
Labels: candidate_oak_1_8 (was: candidate_oak_1_22
candidate_oak_1_8)
Merged into 1.22 branch with PR #716
> Removal (purge) of version of a node does not remove associated labels
> --
>
> Key: OAK-9891
> URL: https://issues.apache.org/jira/browse/OAK-9891
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Arun Kumar Ram
>Assignee: Marcel Reutegger
>Priority: Major
> Labels: candidate_oak_1_8
> Fix For: 1.46.0, 1.22.13
>
> Attachments:
> OAK-9891_removal_of_version_should_remove_associated_labels.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We have encountered a behavior of versionStorage and versionLabels which I
> think is bug.
> *Current behavior:*
>
> # Create a node and make it *versionable*
> # Now create more than two versions (for example two version is *1.0* and
> *1.1* respectively)
> # Now add label at version 1.0 via *VersionHistory* Object (for example
> label is {*}Label_1.0{*})
> # Now remove the version 1.0 via calling *removeVersion(1.0)* method of
> *VersionHistory* object
> # Now call method *hasVersionLabel(Label_1.0)* of versionHistory . its now
> returning true.
>
> *Expected behaviour:*
> Call to the *hasVersionLabel(Label_1.0)* of *versionHistory* should not
> return true because version associated with label does not exist. And
> removing the version should remove associated labels.
>
> If we say that *hasVersionLabel(Label_1.0)* of *versionHistory* returning
> true is expected behavior because label is not removed. Then call to the
> function getVersionByLabel({*}Label_1.0) of versionHistory{*} will ** throw
> VersionException because version does not exist. So the repository goes into
> inconsistent state.
> *Solution proposal:*
> One of the solution can be that whenever consumer of versionHistory removes
> the version , he should be forced to remove the versionLabel first by
> throwing LabelExistException
>
> Another solution can be we should remove version label whenever user removes
> the version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9946) Consistency check for versionable nodes
[ https://issues.apache.org/jira/browse/OAK-9946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9946. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged PR. > Consistency check for versionable nodes > --- > > Key: OAK-9946 > URL: https://issues.apache.org/jira/browse/OAK-9946 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: oak-run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.46.0 > > > This builds on OAK-9918 and adds checks for versionable nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9946) Consistency check for versionable nodes
Marcel Reutegger created OAK-9946: - Summary: Consistency check for versionable nodes Key: OAK-9946 URL: https://issues.apache.org/jira/browse/OAK-9946 Project: Jackrabbit Oak Issue Type: Improvement Components: oak-run Reporter: Marcel Reutegger Assignee: Marcel Reutegger This builds on OAK-9918 and adds checks for versionable nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9918) DocumentNodeStore consistency check
[ https://issues.apache.org/jira/browse/OAK-9918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9918. --- Fix Version/s: 1.46.0 Resolution: Fixed PR merged. > DocumentNodeStore consistency check > --- > > Key: OAK-9918 > URL: https://issues.apache.org/jira/browse/OAK-9918 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.46.0 > > > Create a DocumentNodeStore consistency check in oak-run. > Initially the check should be able to identify orphaned nodes. Later the > check could be extended to check consistency of other data structures like > split documents, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9082) Remove unnecessary (un)boxing in oak-store-composite
[ https://issues.apache.org/jira/browse/OAK-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9082. --- Resolution: Won't Fix Resolving as WONTFIX because the proposed changes are unrelated to boxing (Long.valueOf() vs Long.parseLong()). > Remove unnecessary (un)boxing in oak-store-composite > > > Key: OAK-9082 > URL: https://issues.apache.org/jira/browse/OAK-9082 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: store-composite >Reporter: Lars Grefer >Priority: Major > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/226 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9083) Remove unnecessary (un)boxing in oak-store-document
[ https://issues.apache.org/jira/browse/OAK-9083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9083. --- Resolution: Won't Fix Resolving as WONTFIX for reasons mentioned by Julian. > Remove unnecessary (un)boxing in oak-store-document > --- > > Key: OAK-9083 > URL: https://issues.apache.org/jira/browse/OAK-9083 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: documentmk >Reporter: Lars Grefer >Priority: Minor > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/227 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9084) Remove unnecessary (un)boxing in oak-store-spi
[ https://issues.apache.org/jira/browse/OAK-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9084. --- Fix Version/s: 1.46.0 Resolution: Fixed PR looks good to me and I merged it. Lars, thanks for your contribution. > Remove unnecessary (un)boxing in oak-store-spi > -- > > Key: OAK-9084 > URL: https://issues.apache.org/jira/browse/OAK-9084 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Lars Grefer >Assignee: Marcel Reutegger >Priority: Major > Fix For: 1.46.0 > > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/228 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9084) Remove unnecessary (un)boxing in oak-store-spi
[ https://issues.apache.org/jira/browse/OAK-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9084: - Assignee: Marcel Reutegger > Remove unnecessary (un)boxing in oak-store-spi > -- > > Key: OAK-9084 > URL: https://issues.apache.org/jira/browse/OAK-9084 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Lars Grefer >Assignee: Marcel Reutegger >Priority: Major > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/228 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9085) Remove unnecessary (un)boxing in oak-webapp
[ https://issues.apache.org/jira/browse/OAK-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9085. --- Fix Version/s: 1.46.0 Resolution: Fixed PR looks good to me and I merged it. Lars, thanks for your contribution. > Remove unnecessary (un)boxing in oak-webapp > --- > > Key: OAK-9085 > URL: https://issues.apache.org/jira/browse/OAK-9085 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples, webapp >Reporter: Lars Grefer >Assignee: Marcel Reutegger >Priority: Major > Fix For: 1.46.0 > > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/229 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9085) Remove unnecessary (un)boxing in oak-webapp
[ https://issues.apache.org/jira/browse/OAK-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9085: - Assignee: Marcel Reutegger > Remove unnecessary (un)boxing in oak-webapp > --- > > Key: OAK-9085 > URL: https://issues.apache.org/jira/browse/OAK-9085 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples, webapp >Reporter: Lars Grefer >Assignee: Marcel Reutegger >Priority: Major > > The patch can be found here: https://github.com/apache/jackrabbit-oak/pull/229 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9935) Bump Elasticsearch clients from 7.17.3 to 7.17.6
[ https://issues.apache.org/jira/browse/OAK-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9935: -- Fix Version/s: 1.46.0 Description: [~nuno.santos], [~joerghoh] please set a fix version when you resolve and issue. > Bump Elasticsearch clients from 7.17.3 to 7.17.6 > > > Key: OAK-9935 > URL: https://issues.apache.org/jira/browse/OAK-9935 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Fix For: 1.46.0 > > > [~nuno.santos], [~joerghoh] please set a fix version when you resolve and > issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9925) update MongoDB Java Driver dependency to 3.12.11
[ https://issues.apache.org/jira/browse/OAK-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605699#comment-17605699 ] Marcel Reutegger commented on OAK-9925: --- There is also ongoing work to update the driver to 4.x. See OAK-9447 > update MongoDB Java Driver dependency to 3.12.11 > > > Key: OAK-9925 > URL: https://issues.apache.org/jira/browse/OAK-9925 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.46.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9447) Upgrade Mongo java driver to 4.7
[ https://issues.apache.org/jira/browse/OAK-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9447: - Assignee: José Andrés Cordero Benítez [~corderob], assigning to you, because you are working on this. > Upgrade Mongo java driver to 4.7 > > > Key: OAK-9447 > URL: https://issues.apache.org/jira/browse/OAK-9447 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: José Andrés Cordero Benítez >Assignee: José Andrés Cordero Benítez >Priority: Major > > Upgrade Mongo java driver to 4.2+ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9447) Upgrade Mongo java driver to 4.7
[ https://issues.apache.org/jira/browse/OAK-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9447: -- Summary: Upgrade Mongo java driver to 4.7 (was: Upgrade Mongo java driver to 4.2) > Upgrade Mongo java driver to 4.7 > > > Key: OAK-9447 > URL: https://issues.apache.org/jira/browse/OAK-9447 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: José Andrés Cordero Benítez >Priority: Major > > Upgrade Mongo java driver to 4.2+ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9939) Build failure: Container startup failed
[
https://issues.apache.org/jira/browse/OAK-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9939:
--
Component/s: elastic-search
Description:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #634 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#634|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/console]
{noformat}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 236.574
s <<< FAILURE! - in
org.apache.jackrabbit.oak.plugins.index.elastic.index.ElasticIndexWriterDisabledTest
[ERROR]
org.apache.jackrabbit.oak.plugins.index.elastic.index.ElasticIndexWriterDisabledTest
Time elapsed: 236.573 s <<< ERROR!
org.testcontainers.containers.ContainerLaunchException: Container startup failed
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:349)
at
org.testcontainers.containers.GenericContainer.start(GenericContainer.java:322)
at
org.apache.jackrabbit.oak.plugins.index.elastic.ElasticTestServer.setup(ElasticTestServer.java:86)
at
org.apache.jackrabbit.oak.plugins.index.elastic.ElasticTestServer.getESTestServer(ElasticTestServer.java:57)
at
org.apache.jackrabbit.oak.plugins.index.elastic.ElasticConnectionRule.apply(ElasticConnectionRule.java:63)
at org.junit.rules.RunRules.applyAll(RunRules.java:26)
at org.junit.rules.RunRules.(RunRules.java:15)
at org.junit.runners.ParentRunner.withClassRules(ParentRunner.java:269)
at org.junit.runners.ParentRunner.classBlock(ParentRunner.java:217)
at org.junit.runners.ParentRunner.run(ParentRunner.java:412)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
with exception
at
org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:334)
... 17 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
create/start container
at
org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:542)
at
org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:344)
at
org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
... 18 more
Caused by: java.lang.IllegalStateException: Container exited with code 1
at
org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:514)
... 20 more
{noformat}
was:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #634 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#634|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/console]
> Build failure: Container startup failed
> ---
>
> Key: OAK-9939
> URL: https://issues.apache.org/jira/browse/OAK-9939
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, elastic-search
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #634 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #634|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/console]
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 236.574 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.plugins.index.elastic.index.ElasticIndexWriterDisabledTest
> [ERROR]
> org.apache.jackrabbit.oak.plugins.index.elastic.index.ElasticIndexWriterDisabledTest
> Time elapsed: 236.573 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
>
[jira] [Updated] (OAK-9939) Build failure: Container startup failed
[ https://issues.apache.org/jira/browse/OAK-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9939: -- Summary: Build failure: Container startup failed (was: Build Jackrabbit/jackrabbit-oak-trunk #634 failed) > Build failure: Container startup failed > --- > > Key: OAK-9939 > URL: https://issues.apache.org/jira/browse/OAK-9939 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #634 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #634|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/634/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9937) Build timeout
[ https://issues.apache.org/jira/browse/OAK-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9937: -- Summary: Build timeout (was: Build Jackrabbit/jackrabbit-oak-trunk #631 failed) > Build timeout > - > > Key: OAK-9937 > URL: https://issues.apache.org/jira/browse/OAK-9937 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #631 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #631|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/631/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/631/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9923) Build Jackrabbit/jackrabbit-oak-trunk #624 failed
[
https://issues.apache.org/jira/browse/OAK-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-9923.
---
Resolution: Duplicate
> Build Jackrabbit/jackrabbit-oak-trunk #624 failed
> -
>
> Key: OAK-9923
> URL: https://issues.apache.org/jira/browse/OAK-9923
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #624 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #624|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/console]
> Two failures:
> {noformat}
> [INFO] Running org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 107.693 s <<< FAILURE! - in org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] heavyWrite(org.apache.jackrabbit.oak.segment.HeavyWriteIT) Time
> elapsed: 106.938 s <<< ERROR!
> java.io.IOException: No space left on device
> at java.io.RandomAccessFile.writeBytes(Native Method)
> at java.io.RandomAccessFile.write(RandomAccessFile.java:525)
> at
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarWriter.writeSegment(SegmentTarWriter.java:120)
> at
> org.apache.jackrabbit.oak.segment.file.tar.TarWriter.writeEntry(TarWriter.java:144)
> at
> org.apache.jackrabbit.oak.segment.file.tar.TarFiles.writeSegment(TarFiles.java:597)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.writeSegment(FileStore.java:555)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.internalWriteStream(DefaultSegmentWriter.java:686)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.writeStream(DefaultSegmentWriter.java:629)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.access$500(DefaultSegmentWriter.java:215)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter.writeStream(DefaultSegmentWriter.java:193)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeStore.createBlob(SegmentNodeStore.java:247)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createBlob(HeavyWriteIT.java:125)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createProperties(HeavyWriteIT.java:118)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:110)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:111)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.heavyWrite(HeavyWriteIT.java:91)
> {noformat}
> and
> {noformat}
> [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 156.4 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> [ERROR]
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 72.162 s <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:120)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.jackrabbit.oak.segment.standby.DataStoreTestBase.testSyncBigBlob(DataStoreTestBase.java:299)
> {noformat}
> The first looks like an infra issue and the second one is a duplicate of
> OAK-9920.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9923) Build Jackrabbit/jackrabbit-oak-trunk #624 failed
[
https://issues.apache.org/jira/browse/OAK-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9923:
--
Description:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #624 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#624|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/console]
Two failures:
{noformat}
[INFO] Running org.apache.jackrabbit.oak.segment.HeavyWriteIT
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 107.693
s <<< FAILURE! - in org.apache.jackrabbit.oak.segment.HeavyWriteIT
[ERROR] heavyWrite(org.apache.jackrabbit.oak.segment.HeavyWriteIT) Time
elapsed: 106.938 s <<< ERROR!
java.io.IOException: No space left on device
at java.io.RandomAccessFile.writeBytes(Native Method)
at java.io.RandomAccessFile.write(RandomAccessFile.java:525)
at
org.apache.jackrabbit.oak.segment.file.tar.SegmentTarWriter.writeSegment(SegmentTarWriter.java:120)
at
org.apache.jackrabbit.oak.segment.file.tar.TarWriter.writeEntry(TarWriter.java:144)
at
org.apache.jackrabbit.oak.segment.file.tar.TarFiles.writeSegment(TarFiles.java:597)
at
org.apache.jackrabbit.oak.segment.file.FileStore.writeSegment(FileStore.java:555)
at
org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.internalWriteStream(DefaultSegmentWriter.java:686)
at
org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.writeStream(DefaultSegmentWriter.java:629)
at
org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.access$500(DefaultSegmentWriter.java:215)
at
org.apache.jackrabbit.oak.segment.DefaultSegmentWriter.writeStream(DefaultSegmentWriter.java:193)
at
org.apache.jackrabbit.oak.segment.SegmentNodeStore.createBlob(SegmentNodeStore.java:247)
at
org.apache.jackrabbit.oak.segment.HeavyWriteIT.createBlob(HeavyWriteIT.java:125)
at
org.apache.jackrabbit.oak.segment.HeavyWriteIT.createProperties(HeavyWriteIT.java:118)
at
org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:110)
at
org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:111)
at
org.apache.jackrabbit.oak.segment.HeavyWriteIT.heavyWrite(HeavyWriteIT.java:91)
{noformat}
and
{noformat}
[ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 156.4
s <<< FAILURE! - in
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
[ERROR]
testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
Time elapsed: 72.162 s <<< FAILURE!
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.jackrabbit.oak.segment.standby.DataStoreTestBase.testSyncBigBlob(DataStoreTestBase.java:299)
{noformat}
The first looks like an infra issue and the second one is a duplicate of
OAK-9920.
was:
No description is provided
The build Jackrabbit/jackrabbit-oak-trunk #624 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk
#624|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/]
[console
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/console]
> Build Jackrabbit/jackrabbit-oak-trunk #624 failed
> -
>
> Key: OAK-9923
> URL: https://issues.apache.org/jira/browse/OAK-9923
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #624 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #624|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/console]
> Two failures:
> {noformat}
> [INFO] Running org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 107.693 s <<< FAILURE! - in org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] heavyWrite(org.apache.jackrabbit.oak.segment.HeavyWriteIT) Time
> elapsed: 106.938 s <<< ERROR!
> java.io.IOException: No space left on device
> at java.io.RandomAccessFile.writeBytes(Native Method)
> at java.io.RandomAccessFile.write(RandomAccessFile.java:525)
> at
>
[jira] [Closed] (OAK-9923) Build Jackrabbit/jackrabbit-oak-trunk #624 failed
[
https://issues.apache.org/jira/browse/OAK-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger closed OAK-9923.
-
> Build Jackrabbit/jackrabbit-oak-trunk #624 failed
> -
>
> Key: OAK-9923
> URL: https://issues.apache.org/jira/browse/OAK-9923
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit/jackrabbit-oak-trunk #624 has failed.
> First failed run: [Jackrabbit/jackrabbit-oak-trunk
> #624|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/]
> [console
> log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/624/console]
> Two failures:
> {noformat}
> [INFO] Running org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 107.693 s <<< FAILURE! - in org.apache.jackrabbit.oak.segment.HeavyWriteIT
> [ERROR] heavyWrite(org.apache.jackrabbit.oak.segment.HeavyWriteIT) Time
> elapsed: 106.938 s <<< ERROR!
> java.io.IOException: No space left on device
> at java.io.RandomAccessFile.writeBytes(Native Method)
> at java.io.RandomAccessFile.write(RandomAccessFile.java:525)
> at
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarWriter.writeSegment(SegmentTarWriter.java:120)
> at
> org.apache.jackrabbit.oak.segment.file.tar.TarWriter.writeEntry(TarWriter.java:144)
> at
> org.apache.jackrabbit.oak.segment.file.tar.TarFiles.writeSegment(TarFiles.java:597)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.writeSegment(FileStore.java:555)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.internalWriteStream(DefaultSegmentWriter.java:686)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.writeStream(DefaultSegmentWriter.java:629)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter$SegmentWriteOperation.access$500(DefaultSegmentWriter.java:215)
> at
> org.apache.jackrabbit.oak.segment.DefaultSegmentWriter.writeStream(DefaultSegmentWriter.java:193)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeStore.createBlob(SegmentNodeStore.java:247)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createBlob(HeavyWriteIT.java:125)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createProperties(HeavyWriteIT.java:118)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:110)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.createNodes(HeavyWriteIT.java:111)
> at
> org.apache.jackrabbit.oak.segment.HeavyWriteIT.heavyWrite(HeavyWriteIT.java:91)
> {noformat}
> and
> {noformat}
> [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 156.4 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> [ERROR]
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 72.162 s <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:120)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.jackrabbit.oak.segment.standby.DataStoreTestBase.testSyncBigBlob(DataStoreTestBase.java:299)
> {noformat}
> The first looks like an infra issue and the second one is a duplicate of
> OAK-9920.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OAK-9835) Build Jackrabbit/jackrabbit-oak-trunk #565 failed
[ https://issues.apache.org/jira/browse/OAK-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9835. - > Build Jackrabbit/jackrabbit-oak-trunk #565 failed > - > > Key: OAK-9835 > URL: https://issues.apache.org/jira/browse/OAK-9835 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #565 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #565|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/565/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/565/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9820) Build Jackrabbit/jackrabbit-oak-trunk #556 failed
[ https://issues.apache.org/jira/browse/OAK-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9820. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #556 failed > - > > Key: OAK-9820 > URL: https://issues.apache.org/jira/browse/OAK-9820 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #556 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #556|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/556/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/556/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9820) Build Jackrabbit/jackrabbit-oak-trunk #556 failed
[ https://issues.apache.org/jira/browse/OAK-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9820. - > Build Jackrabbit/jackrabbit-oak-trunk #556 failed > - > > Key: OAK-9820 > URL: https://issues.apache.org/jira/browse/OAK-9820 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #556 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #556|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/556/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/556/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9835) Build Jackrabbit/jackrabbit-oak-trunk #565 failed
[ https://issues.apache.org/jira/browse/OAK-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9835. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #565 failed > - > > Key: OAK-9835 > URL: https://issues.apache.org/jira/browse/OAK-9835 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #565 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #565|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/565/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/565/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9882) Build Jackrabbit/jackrabbit-oak-trunk #592 failed
[ https://issues.apache.org/jira/browse/OAK-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9882. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #592 failed > - > > Key: OAK-9882 > URL: https://issues.apache.org/jira/browse/OAK-9882 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #592 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #592|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/592/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/592/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9882) Build Jackrabbit/jackrabbit-oak-trunk #592 failed
[ https://issues.apache.org/jira/browse/OAK-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9882. - > Build Jackrabbit/jackrabbit-oak-trunk #592 failed > - > > Key: OAK-9882 > URL: https://issues.apache.org/jira/browse/OAK-9882 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #592 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #592|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/592/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/592/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9768) Build Jackrabbit/jackrabbit-oak-trunk #514 failed
[ https://issues.apache.org/jira/browse/OAK-9768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9768. - > Build Jackrabbit/jackrabbit-oak-trunk #514 failed > - > > Key: OAK-9768 > URL: https://issues.apache.org/jira/browse/OAK-9768 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #514 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #514|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/514/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/514/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9818) Build Jackrabbit/jackrabbit-oak-trunk #551 failed
[ https://issues.apache.org/jira/browse/OAK-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9818. - > Build Jackrabbit/jackrabbit-oak-trunk #551 failed > - > > Key: OAK-9818 > URL: https://issues.apache.org/jira/browse/OAK-9818 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #551 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #551|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/551/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/551/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9742) Build Jackrabbit/jackrabbit-oak-trunk #497 failed
[ https://issues.apache.org/jira/browse/OAK-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9742. - > Build Jackrabbit/jackrabbit-oak-trunk #497 failed > - > > Key: OAK-9742 > URL: https://issues.apache.org/jira/browse/OAK-9742 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #497 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #497|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/497/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/497/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9818) Build Jackrabbit/jackrabbit-oak-trunk #551 failed
[ https://issues.apache.org/jira/browse/OAK-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9818. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #551 failed > - > > Key: OAK-9818 > URL: https://issues.apache.org/jira/browse/OAK-9818 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #551 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #551|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/551/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/551/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9805) Build Jackrabbit/jackrabbit-oak-trunk #538 failed
[ https://issues.apache.org/jira/browse/OAK-9805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9805. - > Build Jackrabbit/jackrabbit-oak-trunk #538 failed > - > > Key: OAK-9805 > URL: https://issues.apache.org/jira/browse/OAK-9805 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #538 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #538|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/538/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/538/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9805) Build Jackrabbit/jackrabbit-oak-trunk #538 failed
[ https://issues.apache.org/jira/browse/OAK-9805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9805. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #538 failed > - > > Key: OAK-9805 > URL: https://issues.apache.org/jira/browse/OAK-9805 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #538 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #538|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/538/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/538/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9768) Build Jackrabbit/jackrabbit-oak-trunk #514 failed
[ https://issues.apache.org/jira/browse/OAK-9768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9768. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #514 failed > - > > Key: OAK-9768 > URL: https://issues.apache.org/jira/browse/OAK-9768 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #514 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #514|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/514/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/514/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9742) Build Jackrabbit/jackrabbit-oak-trunk #497 failed
[ https://issues.apache.org/jira/browse/OAK-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9742. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #497 failed > - > > Key: OAK-9742 > URL: https://issues.apache.org/jira/browse/OAK-9742 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #497 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #497|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/497/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/497/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9597) Build Jackrabbit/jackrabbit-oak-trunk #368 failed
[ https://issues.apache.org/jira/browse/OAK-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9597. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #368 failed > - > > Key: OAK-9597 > URL: https://issues.apache.org/jira/browse/OAK-9597 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #368 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #368|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/368/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/368/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9622) Build Jackrabbit/jackrabbit-oak-trunk #397 failed
[ https://issues.apache.org/jira/browse/OAK-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9622. - > Build Jackrabbit/jackrabbit-oak-trunk #397 failed > - > > Key: OAK-9622 > URL: https://issues.apache.org/jira/browse/OAK-9622 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #397 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #397|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/397/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/397/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9698) Build Jackrabbit/jackrabbit-oak-trunk #463 failed
[ https://issues.apache.org/jira/browse/OAK-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9698. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #463 failed > - > > Key: OAK-9698 > URL: https://issues.apache.org/jira/browse/OAK-9698 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #463 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #463|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/463/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/463/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9570) Build Jackrabbit/jackrabbit-oak-trunk #344 failed
[ https://issues.apache.org/jira/browse/OAK-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9570. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #344 failed > - > > Key: OAK-9570 > URL: https://issues.apache.org/jira/browse/OAK-9570 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #344 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #344|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/344/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/344/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9597) Build Jackrabbit/jackrabbit-oak-trunk #368 failed
[ https://issues.apache.org/jira/browse/OAK-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9597. - > Build Jackrabbit/jackrabbit-oak-trunk #368 failed > - > > Key: OAK-9597 > URL: https://issues.apache.org/jira/browse/OAK-9597 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #368 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #368|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/368/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/368/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9622) Build Jackrabbit/jackrabbit-oak-trunk #397 failed
[ https://issues.apache.org/jira/browse/OAK-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9622. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #397 failed > - > > Key: OAK-9622 > URL: https://issues.apache.org/jira/browse/OAK-9622 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #397 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #397|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/397/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/397/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9640) Build Jackrabbit/jackrabbit-oak-trunk #412 failed
[ https://issues.apache.org/jira/browse/OAK-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9640. - > Build Jackrabbit/jackrabbit-oak-trunk #412 failed > - > > Key: OAK-9640 > URL: https://issues.apache.org/jira/browse/OAK-9640 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #412 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #412|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/412/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/412/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9698) Build Jackrabbit/jackrabbit-oak-trunk #463 failed
[ https://issues.apache.org/jira/browse/OAK-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9698. - > Build Jackrabbit/jackrabbit-oak-trunk #463 failed > - > > Key: OAK-9698 > URL: https://issues.apache.org/jira/browse/OAK-9698 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #463 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #463|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/463/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/463/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9640) Build Jackrabbit/jackrabbit-oak-trunk #412 failed
[ https://issues.apache.org/jira/browse/OAK-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9640. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #412 failed > - > > Key: OAK-9640 > URL: https://issues.apache.org/jira/browse/OAK-9640 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #412 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #412|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/412/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/412/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9570) Build Jackrabbit/jackrabbit-oak-trunk #344 failed
[ https://issues.apache.org/jira/browse/OAK-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9570. - > Build Jackrabbit/jackrabbit-oak-trunk #344 failed > - > > Key: OAK-9570 > URL: https://issues.apache.org/jira/browse/OAK-9570 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #344 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #344|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/344/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/344/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9549) Build Jackrabbit/jackrabbit-oak-trunk #325 failed
[ https://issues.apache.org/jira/browse/OAK-9549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9549. - > Build Jackrabbit/jackrabbit-oak-trunk #325 failed > - > > Key: OAK-9549 > URL: https://issues.apache.org/jira/browse/OAK-9549 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #325 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #325|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/325/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/325/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9549) Build Jackrabbit/jackrabbit-oak-trunk #325 failed
[ https://issues.apache.org/jira/browse/OAK-9549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9549. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #325 failed > - > > Key: OAK-9549 > URL: https://issues.apache.org/jira/browse/OAK-9549 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #325 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #325|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/325/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/325/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9904) Build Jackrabbit/jackrabbit-oak-trunk #609 failed
[ https://issues.apache.org/jira/browse/OAK-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9904. - > Build Jackrabbit/jackrabbit-oak-trunk #609 failed > - > > Key: OAK-9904 > URL: https://issues.apache.org/jira/browse/OAK-9904 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #609 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #609|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/609/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/609/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9542) Build Jackrabbit/jackrabbit-oak-trunk #321 failed
[ https://issues.apache.org/jira/browse/OAK-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9542. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #321 failed > - > > Key: OAK-9542 > URL: https://issues.apache.org/jira/browse/OAK-9542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #321 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #321|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-9542) Build Jackrabbit/jackrabbit-oak-trunk #321 failed
[ https://issues.apache.org/jira/browse/OAK-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-9542. - > Build Jackrabbit/jackrabbit-oak-trunk #321 failed > - > > Key: OAK-9542 > URL: https://issues.apache.org/jira/browse/OAK-9542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #321 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #321|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9898) Introduce github workflow for stale PRs
[ https://issues.apache.org/jira/browse/OAK-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605665#comment-17605665 ] Marcel Reutegger commented on OAK-9898: --- Looks like this issue can be resolved. [~joerghoh] WDYT? > Introduce github workflow for stale PRs > --- > > Key: OAK-9898 > URL: https://issues.apache.org/jira/browse/OAK-9898 > Project: Jackrabbit Oak > Issue Type: Task > Components: continuous integration >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > > We should limit the WIP and therefor try to cleanup open PRs on github if > they are open for too long. > We should use the [Github stale action|https://github.com/actions/stale] to > tag PRs which are open for more than 2 years with the flag "stale" and close > them if this flag is attached to it for more than 60 days. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9904) Build Jackrabbit/jackrabbit-oak-trunk #609 failed
[ https://issues.apache.org/jira/browse/OAK-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9904. --- Resolution: Cannot Reproduce Logs from initial failure are not available anymore. Resolving as cannot reproduce. > Build Jackrabbit/jackrabbit-oak-trunk #609 failed > - > > Key: OAK-9904 > URL: https://issues.apache.org/jira/browse/OAK-9904 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #609 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #609|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/609/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/609/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9920) ExternalPrivateStoreIT.testSyncBigBlob failures
[
https://issues.apache.org/jira/browse/OAK-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605660#comment-17605660
]
Marcel Reutegger commented on OAK-9920:
---
PR #687 is merged. [~adulceanu], does this resolve the problem described in
this issue?
> ExternalPrivateStoreIT.testSyncBigBlob failures
> ---
>
> Key: OAK-9920
> URL: https://issues.apache.org/jira/browse/OAK-9920
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
>Affects Versions: 1.44.0
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Attachments: console.log
>
>
> {noformat}
> [INFO] Running
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT[ERROR] Tests
> run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 223.509 s <<<
> FAILURE! - in org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> [ERROR]
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 140.744 s <<< FAILURE!java.lang.AssertionError: expected:<\{
> root = { ... } }> but was:<\{ root : { } }>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:120)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.jackrabbit.oak.segment.standby.DataStoreTestBase.testSyncBigBlob(DataStoreTestBase.java:299)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
>
[jira] [Updated] (OAK-9891) Removal (purge) of version of a node does not remove associated labels
[
https://issues.apache.org/jira/browse/OAK-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9891:
--
Labels: candidate_oak_1_22 candidate_oak_1_8 (was: )
> Removal (purge) of version of a node does not remove associated labels
> --
>
> Key: OAK-9891
> URL: https://issues.apache.org/jira/browse/OAK-9891
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Arun Kumar Ram
>Assignee: Marcel Reutegger
>Priority: Major
> Labels: candidate_oak_1_22, candidate_oak_1_8
> Fix For: 1.46.0
>
> Attachments:
> OAK-9891_removal_of_version_should_remove_associated_labels.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We have encountered a behavior of versionStorage and versionLabels which I
> think is bug.
> *Current behavior:*
>
> # Create a node and make it *versionable*
> # Now create more than two versions (for example two version is *1.0* and
> *1.1* respectively)
> # Now add label at version 1.0 via *VersionHistory* Object (for example
> label is {*}Label_1.0{*})
> # Now remove the version 1.0 via calling *removeVersion(1.0)* method of
> *VersionHistory* object
> # Now call method *hasVersionLabel(Label_1.0)* of versionHistory . its now
> returning true.
>
> *Expected behaviour:*
> Call to the *hasVersionLabel(Label_1.0)* of *versionHistory* should not
> return true because version associated with label does not exist. And
> removing the version should remove associated labels.
>
> If we say that *hasVersionLabel(Label_1.0)* of *versionHistory* returning
> true is expected behavior because label is not removed. Then call to the
> function getVersionByLabel({*}Label_1.0) of versionHistory{*} will ** throw
> VersionException because version does not exist. So the repository goes into
> inconsistent state.
> *Solution proposal:*
> One of the solution can be that whenever consumer of versionHistory removes
> the version , he should be forced to remove the versionLabel first by
> throwing LabelExistException
>
> Another solution can be we should remove version label whenever user removes
> the version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9891) Removal (purge) of version of a node does not remove associated labels
[
https://issues.apache.org/jira/browse/OAK-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-9891.
---
Fix Version/s: 1.46.0
Resolution: Fixed
> Removal (purge) of version of a node does not remove associated labels
> --
>
> Key: OAK-9891
> URL: https://issues.apache.org/jira/browse/OAK-9891
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Arun Kumar Ram
>Assignee: Marcel Reutegger
>Priority: Major
> Fix For: 1.46.0
>
> Attachments:
> OAK-9891_removal_of_version_should_remove_associated_labels.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We have encountered a behavior of versionStorage and versionLabels which I
> think is bug.
> *Current behavior:*
>
> # Create a node and make it *versionable*
> # Now create more than two versions (for example two version is *1.0* and
> *1.1* respectively)
> # Now add label at version 1.0 via *VersionHistory* Object (for example
> label is {*}Label_1.0{*})
> # Now remove the version 1.0 via calling *removeVersion(1.0)* method of
> *VersionHistory* object
> # Now call method *hasVersionLabel(Label_1.0)* of versionHistory . its now
> returning true.
>
> *Expected behaviour:*
> Call to the *hasVersionLabel(Label_1.0)* of *versionHistory* should not
> return true because version associated with label does not exist. And
> removing the version should remove associated labels.
>
> If we say that *hasVersionLabel(Label_1.0)* of *versionHistory* returning
> true is expected behavior because label is not removed. Then call to the
> function getVersionByLabel({*}Label_1.0) of versionHistory{*} will ** throw
> VersionException because version does not exist. So the repository goes into
> inconsistent state.
> *Solution proposal:*
> One of the solution can be that whenever consumer of versionHistory removes
> the version , he should be forced to remove the versionLabel first by
> throwing LabelExistException
>
> Another solution can be we should remove version label whenever user removes
> the version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-9891) Removal (purge) of version of a node does not remove associated labels
[
https://issues.apache.org/jira/browse/OAK-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605630#comment-17605630
]
Marcel Reutegger commented on OAK-9891:
---
[~arun92ram], thank you for the PR. Looks good and I merged it.
Behaviour of Oak is now in line with Jackrabbit classic. Any label associated
with a version that gets removed will also be removed automatically.
> Removal (purge) of version of a node does not remove associated labels
> --
>
> Key: OAK-9891
> URL: https://issues.apache.org/jira/browse/OAK-9891
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Arun Kumar Ram
>Assignee: Marcel Reutegger
>Priority: Major
> Attachments:
> OAK-9891_removal_of_version_should_remove_associated_labels.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We have encountered a behavior of versionStorage and versionLabels which I
> think is bug.
> *Current behavior:*
>
> # Create a node and make it *versionable*
> # Now create more than two versions (for example two version is *1.0* and
> *1.1* respectively)
> # Now add label at version 1.0 via *VersionHistory* Object (for example
> label is {*}Label_1.0{*})
> # Now remove the version 1.0 via calling *removeVersion(1.0)* method of
> *VersionHistory* object
> # Now call method *hasVersionLabel(Label_1.0)* of versionHistory . its now
> returning true.
>
> *Expected behaviour:*
> Call to the *hasVersionLabel(Label_1.0)* of *versionHistory* should not
> return true because version associated with label does not exist. And
> removing the version should remove associated labels.
>
> If we say that *hasVersionLabel(Label_1.0)* of *versionHistory* returning
> true is expected behavior because label is not removed. Then call to the
> function getVersionByLabel({*}Label_1.0) of versionHistory{*} will ** throw
> VersionException because version does not exist. So the repository goes into
> inconsistent state.
> *Solution proposal:*
> One of the solution can be that whenever consumer of versionHistory removes
> the version , he should be forced to remove the versionLabel first by
> throwing LabelExistException
>
> Another solution can be we should remove version label whenever user removes
> the version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9535) Support recovery of large branch merge
[
https://issues.apache.org/jira/browse/OAK-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9535:
--
Labels: candidate_oak_1_8 (was: )
> Support recovery of large branch merge
> --
>
> Key: OAK-9535
> URL: https://issues.apache.org/jira/browse/OAK-9535
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
>Affects Versions: 1.40.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Major
> Labels: candidate_oak_1_8
> Fix For: 1.42.0, 1.22.13
>
>
> When branch changes get too large, they are committed and a journal entry is
> created as a result. This way, journal entries - in terms of their byte size
> they use up - cannot grow large.
> When a recovery happenes the mechanism is slightly different: The recovery
> attempts to store a single big journal entry. In case of MongoDB, this can
> result in the document to be larger than 16MB and below exception.
> The recovery must create multiple journal entries as well to avoid running
> into the MongoDB document size limit.
> {noformat}
> Payload document size is larger than maximum of 16777216.
> org.bson.BsonMaximumSizeExceededException: Payload document size is larger
> than maximum of 16777216.
> at
> com.mongodb.internal.connection.BsonWriterHelper.writePayload(BsonWriterHelper.java:68)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encodeMessageBodyWithMetadata(CommandMessage.java:147)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.RequestMessage.encode(RequestMessage.java:138)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encode(CommandMessage.java:61)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:248)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:99)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:450)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:226)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:269)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:131)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeCommand(MixedBulkWriteOperation.java:435)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeBulkWriteBatch(MixedBulkWriteOperation.java:261)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.access$700(MixedBulkWriteOperation.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:205)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.OperationHelper.withReleasableConnection(OperationHelper.java:501)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:71)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:211)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.executeInsertMany(MongoCollectionImpl.java:529)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:524)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:518)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
>
[jira] [Commented] (OAK-9934) backport Oak-9535 to 1.8 branch
[ https://issues.apache.org/jira/browse/OAK-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605277#comment-17605277 ] Marcel Reutegger commented on OAK-9934: --- Yes, I think it would be good to have this fix in the 1.8 branch as well. I recently came across a repository running on 1.8.x with exactly this problem. But let's please move the discussion to OAK-9535. As Julian mentioned, we try to keep the conversation about an problem in the same issue. > backport Oak-9535 to 1.8 branch > --- > > Key: OAK-9934 > URL: https://issues.apache.org/jira/browse/OAK-9934 > Project: Jackrabbit Oak > Issue Type: Bug >Reporter: Rishabh Kumar >Priority: Major > > We need to backport the fixes done in Oak-9535 to 1.8 branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9934) backport Oak-9535 to 1.8 branch
[ https://issues.apache.org/jira/browse/OAK-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9934. --- Resolution: Duplicate > backport Oak-9535 to 1.8 branch > --- > > Key: OAK-9934 > URL: https://issues.apache.org/jira/browse/OAK-9934 > Project: Jackrabbit Oak > Issue Type: Bug >Reporter: Rishabh Kumar >Priority: Major > > We need to backport the fixes done in Oak-9535 to 1.8 branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9933) backport Oak-9535 to 1.22 branch
[ https://issues.apache.org/jira/browse/OAK-9933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9933. --- Resolution: Duplicate I'm resolving this issue as a duplicate of OAK-9535. > backport Oak-9535 to 1.22 branch > > > Key: OAK-9933 > URL: https://issues.apache.org/jira/browse/OAK-9933 > Project: Jackrabbit Oak > Issue Type: Bug >Reporter: Rishabh Kumar >Priority: Major > > We need to backport the fixes done in Oak-9535 to 1.22 branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9535) Support recovery of large branch merge
[
https://issues.apache.org/jira/browse/OAK-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9535:
--
Fix Version/s: 1.22.13
Merged into 1.22 branch with [PR
#701|https://github.com/apache/jackrabbit-oak/pull/701]
> Support recovery of large branch merge
> --
>
> Key: OAK-9535
> URL: https://issues.apache.org/jira/browse/OAK-9535
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
>Affects Versions: 1.40.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Major
> Fix For: 1.42.0, 1.22.13
>
>
> When branch changes get too large, they are committed and a journal entry is
> created as a result. This way, journal entries - in terms of their byte size
> they use up - cannot grow large.
> When a recovery happenes the mechanism is slightly different: The recovery
> attempts to store a single big journal entry. In case of MongoDB, this can
> result in the document to be larger than 16MB and below exception.
> The recovery must create multiple journal entries as well to avoid running
> into the MongoDB document size limit.
> {noformat}
> Payload document size is larger than maximum of 16777216.
> org.bson.BsonMaximumSizeExceededException: Payload document size is larger
> than maximum of 16777216.
> at
> com.mongodb.internal.connection.BsonWriterHelper.writePayload(BsonWriterHelper.java:68)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encodeMessageBodyWithMetadata(CommandMessage.java:147)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.RequestMessage.encode(RequestMessage.java:138)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encode(CommandMessage.java:61)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:248)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:99)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:450)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:226)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:269)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:131)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeCommand(MixedBulkWriteOperation.java:435)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeBulkWriteBatch(MixedBulkWriteOperation.java:261)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.access$700(MixedBulkWriteOperation.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:205)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.OperationHelper.withReleasableConnection(OperationHelper.java:501)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:71)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:211)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.executeInsertMany(MongoCollectionImpl.java:529)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:524)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:518)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
>
[jira] [Created] (OAK-9918) DocumentNodeStore consistency check
Marcel Reutegger created OAK-9918: - Summary: DocumentNodeStore consistency check Key: OAK-9918 URL: https://issues.apache.org/jira/browse/OAK-9918 Project: Jackrabbit Oak Issue Type: New Feature Components: run Reporter: Marcel Reutegger Assignee: Marcel Reutegger Create a DocumentNodeStore consistency check in oak-run. Initially the check should be able to identify orphaned nodes. Later the check could be extended to check consistency of other data structures like split documents, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-8840) move jackrabbit-data into Oak
[
https://issues.apache.org/jira/browse/OAK-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598786#comment-17598786
]
Marcel Reutegger commented on OAK-8840:
---
+1 makes sense to me.
> move jackrabbit-data into Oak
> -
>
> Key: OAK-8840
> URL: https://issues.apache.org/jira/browse/OAK-8840
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: blob
>Reporter: Julian Reschke
>Priority: Major
>
> jackrabbit-data is one of the few remaining dependencies on Jackrabbit. It
> would be good to move this into the Oak project, so it can evolve at Oak's
> speed.
> [~amitj], [~mreutegg], [~mattvryan] - what do you think?
> In particular, are there parts in jackrabbit-data which should stay over
> there? For instance, I assumed that DB-backed data stores aren't used in Oak,
> but then found out about {{DbDataStoreService}}. Maybe a cleanup is needed
> first?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9909) Provide Feature toggle for oplog window based throttling for Mongo Document Store
[ https://issues.apache.org/jira/browse/OAK-9909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9909. --- Fix Version/s: 1.46.0 Resolution: Fixed PR looks good to me. I merged it into trunk. [~rishudaim], thanks for your contribution. > Provide Feature toggle for oplog window based throttling for Mongo Document > Store > - > > Key: OAK-9909 > URL: https://issues.apache.org/jira/browse/OAK-9909 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Rishabh Kumar >Priority: Major > Fix For: 1.46.0 > > > We need to provide support for feature toggle to enable/disable oplog window > based mongo document store throttling. > > With help of this feature toggle, we can either enable/disable throttling on > servers without making any binary changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9855) Enable for Lucene the tests common to Lucene and Elastic that are failing only with Elastic
[
https://issues.apache.org/jira/browse/OAK-9855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9855:
--
Fix Version/s: 1.46.0
> Enable for Lucene the tests common to Lucene and Elastic that are failing
> only with Elastic
> ---
>
> Key: OAK-9855
> URL: https://issues.apache.org/jira/browse/OAK-9855
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
> Fix For: 1.46.0
>
>
> In the tests common between the Lucene and Elastic plugins defined in the
> package {{{}oak-search/test/org.apache.jackrabbit.oak.plugins.index{}}},
> there are some tests disabled on the base class because they do not pass with
> Elastic. But disabling them on the base class prevents them from running in
> the Lucene tests, so we are missing some test coverage and risking
> regressions. These tests should be ignored only on the Elastic implementation
> of the test, so they run with Lucene.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9884) Optimization: use Elastic prefix queries instead of wildcard queries for "like foo%" constraints
[
https://issues.apache.org/jira/browse/OAK-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9884:
--
Fix Version/s: 1.46.0
> Optimization: use Elastic prefix queries instead of wildcard queries for
> "like foo%" constraints
> --
>
> Key: OAK-9884
> URL: https://issues.apache.org/jira/browse/OAK-9884
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
> Fix For: 1.46.0
>
>
> For a query like
> {noformat}
> select * from [nt:base] where [propa] like '12%'{noformat}
> the Elastic module will generate a wildcard query of the form
> {noformat}
> {"bool":{"filter":[{"wildcard":{"propa":{"value":"12*"}}}]}}{noformat}
> But the Elastic query can be done more efficiently with
> {noformat}
> {"bool":{"filter":[{"prefix":{"propa":{"value":"12"}}}]}}{noformat}
> That is, any like condition that has a single wilcard of type % at the end,
> can be rewritten as a prefix query.
> The current code on trunk attempts to implement this optimization, but due to
> an off-by-one bug, the logic that would use prefix queries is never executed.
>
> [https://github.com/apache/jackrabbit-oak/blob/27a7a9ffa0e78e5b258626aef24066eb58efc559/oak-search-elastic/src/main/java/org/apache/jackrabbit/oak/plugins/index/elastic/query/ElasticRequestHandler.java#L750-L771]
> Also see OAK-9881 for a more detailed analysis.
> h3. Context
> Elastic documentation suggests that wilcard queries are expensive:
> [https://www.elastic.co/guide/en/elasticsearch/reference/7.17/query-dsl-wildcard-query.html]
> h4. Allow expensive queries
> Wildcard queries will not be executed if
> [{{search.allow_expensive_queries}}|https://www.elastic.co/guide/en/elasticsearch/reference/7.17/query-dsl.html#query-dsl-allow-expensive-queries]
> is set to false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9874) Add a (failing and @Ignored) unit test to check that queries return same result with and without index.
[
https://issues.apache.org/jira/browse/OAK-9874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9874:
--
Fix Version/s: 1.46.0
[~nuno.santos], please set an appropriate fix version when you resolve an
issue. For a change that went into into trunk that usually means the highest
unreleased 1.x.0 version.
> Add a (failing and @Ignored) unit test to check that queries return same
> result with and without index.
>
>
> Key: OAK-9874
> URL: https://issues.apache.org/jira/browse/OAK-9874
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.46.0
>
>
> Consider the following nodes:
> ||node||propa||
> |/test/long|1234|
> |/test/double|1.11|
> |/test/string_numeric|"1234"|
> |/test/string|"1234a"|
> |/test/boolean_true|true|
> |/test/boolean_false|false|
> And the index:
> {noformat}
> /oak:index/testIndex
> - jcr:primaryType = "oak:QueryIndexDefinition"
> - type = "lucene"
> - compatVersion = 2
> - async = "async"
> + indexRules
> - jcr:primaryType = "nt:unstructured"
> + nt:base
> + properties
> - jcr:primaryType = "nt:unstructured"
> + assetType
> - propertyIndex = true
> - name = "propa"
> - type = "Long"
> {noformat}
>
> The following queries return different results when run with and without
> index:
> {noformat}
> Query: /jcr:root//*[@propa]
> With index: [/test/double, /test/long]
> Without index: [/test/boolean_false, /test/boolean_true, /test/double,
> /test/long, /test/string, /test/string_numeric]
> Query: /jcr:root//*[@propa > 0]
> With index: [/test/double, /test/long]
> Without index: [/test/boolean_true, /test/double, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa > '0']
> With index: [/test/double, /test/long]
> Without index: [/test/boolean_true, /test/double, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa = 1.11]
> With index: []
> Without index: [/test/boolean_false, /test/double]
> Query: /jcr:root//*[@propa = '1.11']
> With index: []
> Without index: [/test/boolean_false, /test/double]
> Query: /jcr:root//*[@propa > 1]
> With index: [/test/double, /test/long]
> Without index: [/test/boolean_true, /test/double, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa > '1']
> With index: [/test/double, /test/long]
> Without index: [/test/boolean_true, /test/double, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa > ]
> With index: [/test/long]
> Without index: [/test/boolean_true, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa > '']
> With index: [/test/long]
> Without index: [/test/boolean_true, /test/long, /test/string,
> /test/string_numeric]
> Query: /jcr:root//*[@propa = true]
> With index: []
> Without index: [/test/boolean_true]
> Query: /jcr:root//*[@propa = 'true']
> With index: []
> Without index: [/test/boolean_true]
> Query: /jcr:root//*[@propa = false]
> With index: []
> Without index: [/test/boolean_false]
> Query: /jcr:root//*[@propa = 'false']
> With index: []
> Without index: [/test/boolean_false]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-9898) Introduce github workflow for stale PRs
[ https://issues.apache.org/jira/browse/OAK-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17585334#comment-17585334 ] Marcel Reutegger commented on OAK-9898: --- +1, I would like us to give this a try. > Introduce github workflow for stale PRs > --- > > Key: OAK-9898 > URL: https://issues.apache.org/jira/browse/OAK-9898 > Project: Jackrabbit Oak > Issue Type: Task > Components: continuous integration >Reporter: Joerg Hoh >Assignee: Joerg Hoh >Priority: Major > > We should limit the WIP and therefor try to cleanup open PRs on github if > they are open for too long. > We should use the [Github stale action|https://github.com/actions/stale] to > tag PRs which are open for more than 2 years with the flag "stale" and close > them if this flag is attached to it for more than 60 days. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9886) Missing tests for like constraint in Elastic
[
https://issues.apache.org/jira/browse/OAK-9886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-9886:
--
Fix Version/s: 1.46.0
> Missing tests for like constraint in Elastic
>
>
> Key: OAK-9886
> URL: https://issues.apache.org/jira/browse/OAK-9886
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.46.0
>
>
> The tests for the like operator in {{LucenePropertyIndexTest}} should be
> moved to the common tests in oak-search, so they are also run with Elastic.
> Currently, there are no Elastic tests for the like constraint.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9908) Recovery may revert committed changes
[ https://issues.apache.org/jira/browse/OAK-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-9908: -- Labels: candidate_oak_1_22 candidate_oak_1_8 (was: ) > Recovery may revert committed changes > - > > Key: OAK-9908 > URL: https://issues.apache.org/jira/browse/OAK-9908 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Affects Versions: 1.8.0, 1.22.0, 1.44.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Critical > Labels: candidate_oak_1_22, candidate_oak_1_8 > Fix For: 1.46.0 > > > Recovery for another clusterId may partially revert recently committed > changes. Whether the issue occurs or not depends on the sequence of documents > checked and whether the DocumentStore cache contains stale documents without > the corresponding commit information. The recovery then incorrectly concludes > certain changes are not committed and reverts them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9908) Recovery may revert committed changes
[ https://issues.apache.org/jira/browse/OAK-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9908. --- Fix Version/s: 1.46.0 Resolution: Fixed Merged PR with proposed fix into trunk. > Recovery may revert committed changes > - > > Key: OAK-9908 > URL: https://issues.apache.org/jira/browse/OAK-9908 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Affects Versions: 1.8.0, 1.22.0, 1.44.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Critical > Fix For: 1.46.0 > > > Recovery for another clusterId may partially revert recently committed > changes. Whether the issue occurs or not depends on the sequence of documents > checked and whether the DocumentStore cache contains stale documents without > the corresponding commit information. The recovery then incorrectly concludes > certain changes are not committed and reverts them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9908) Recovery may revert committed changes
[ https://issues.apache.org/jira/browse/OAK-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583027#comment-17583027 ] Marcel Reutegger commented on OAK-9908: --- PR [#675|https://github.com/apache/jackrabbit-oak/pull/675] proposes a fix. > Recovery may revert committed changes > - > > Key: OAK-9908 > URL: https://issues.apache.org/jira/browse/OAK-9908 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Affects Versions: 1.8.0, 1.22.0, 1.44.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Critical > > Recovery for another clusterId may partially revert recently committed > changes. Whether the issue occurs or not depends on the sequence of documents > checked and whether the DocumentStore cache contains stale documents without > the corresponding commit information. The recovery then incorrectly concludes > certain changes are not committed and reverts them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9908) Recovery may revert committed changes
[ https://issues.apache.org/jira/browse/OAK-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582959#comment-17582959 ] Marcel Reutegger commented on OAK-9908: --- PR [#674|https://github.com/apache/jackrabbit-oak/pull/674] contains a test that reproduces the issue. > Recovery may revert committed changes > - > > Key: OAK-9908 > URL: https://issues.apache.org/jira/browse/OAK-9908 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Affects Versions: 1.8.0, 1.22.0, 1.44.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Critical > > Recovery for another clusterId may partially revert recently committed > changes. Whether the issue occurs or not depends on the sequence of documents > checked and whether the DocumentStore cache contains stale documents without > the corresponding commit information. The recovery then incorrectly concludes > certain changes are not committed and reverts them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9908) Recovery may revert committed changes
Marcel Reutegger created OAK-9908: - Summary: Recovery may revert committed changes Key: OAK-9908 URL: https://issues.apache.org/jira/browse/OAK-9908 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk Affects Versions: 1.44.0, 1.22.0, 1.8.0 Reporter: Marcel Reutegger Assignee: Marcel Reutegger Recovery for another clusterId may partially revert recently committed changes. Whether the issue occurs or not depends on the sequence of documents checked and whether the DocumentStore cache contains stale documents without the corresponding commit information. The recovery then incorrectly concludes certain changes are not committed and reverts them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9851) Provide support for throttling in mongo oak client based on oplog replication window
[ https://issues.apache.org/jira/browse/OAK-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9851. --- Fix Version/s: 1.46.0 Resolution: Fixed Changes in the PR looked good after several review cycles and I merged it. [~rishudaim] thanks for your contribution. > Provide support for throttling in mongo oak client based on oplog replication > window > > > Key: OAK-9851 > URL: https://issues.apache.org/jira/browse/OAK-9851 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Rishabh Kumar >Assignee: Marcel Reutegger >Priority: Major > Fix For: 1.46.0 > > > In prod envs, Mongo works in Primary/Secondary configuration where writes > happens on primary and secondaries replicate them asynchronously from > primary's oplog.rs collection. > > In case there is huge skipe in mongo (may be under huge load or some inernal > sharding) the oplog window can drop to few minutes, thus creating a risk for > secondaries to fall-off oplog window and going into initial-sync phase. > > This can be catastrophic if during this initial-sync phase the primary goes > down and hence mongo will become unavailable and we might need to setup new > cluster from snapshots. > > To avoid this, I propose to add throttling into mongo oak client in case > oplog window drops below a certain threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-9851) Provide support for throttling in mongo oak client based on oplog replication window
[ https://issues.apache.org/jira/browse/OAK-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-9851: - Assignee: Marcel Reutegger > Provide support for throttling in mongo oak client based on oplog replication > window > > > Key: OAK-9851 > URL: https://issues.apache.org/jira/browse/OAK-9851 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Rishabh Kumar >Assignee: Marcel Reutegger >Priority: Major > > In prod envs, Mongo works in Primary/Secondary configuration where writes > happens on primary and secondaries replicate them asynchronously from > primary's oplog.rs collection. > > In case there is huge skipe in mongo (may be under huge load or some inernal > sharding) the oplog window can drop to few minutes, thus creating a risk for > secondaries to fall-off oplog window and going into initial-sync phase. > > This can be catastrophic if during this initial-sync phase the primary goes > down and hence mongo will become unavailable and we might need to setup new > cluster from snapshots. > > To avoid this, I propose to add throttling into mongo oak client in case > oplog window drops below a certain threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
