[jira] [Commented] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
[ https://issues.apache.org/jira/browse/OAK-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817817#comment-17817817 ] Hudson commented on OAK-10654: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1366|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1366/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1366/console] > Build Jackrabbit/jackrabbit-oak-trunk #1363 failed > -- > > Key: OAK-10654 > URL: https://issues.apache.org/jira/browse/OAK-10654 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
[ https://issues.apache.org/jira/browse/OAK-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817767#comment-17817767 ] Hudson commented on OAK-10654: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1365|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1365/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1365/console] > Build Jackrabbit/jackrabbit-oak-trunk #1363 failed > -- > > Key: OAK-10654 > URL: https://issues.apache.org/jira/browse/OAK-10654 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10643) MongoDocumentStore: improve diagnostics for too large docs
[ https://issues.apache.org/jira/browse/OAK-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817488#comment-17817488 ] Julian Reschke edited comment on OAK-10643 at 2/15/24 5:08 PM: --- trunk: [32462bde8b|https://github.com/apache/jackrabbit-oak/commit/32462bde8b1b5fb4ab9e15d37c1d0322605ff3bb] [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] was (Author: reschke): trunk: [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] > MongoDocumentStore: improve diagnostics for too large docs > -- > > Key: OAK-10643 > URL: https://issues.apache.org/jira/browse/OAK-10643 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > > Log or add to exception message (or both): > - attempted UpdateOp > - statistics about the document that was too large to be updated (that would > require a read from Mongo) > Later on, we may want to extend this to that higher layers > (DocumentNodeStore) can try some kind of recovery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount
[
https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-10655:
--
Description:
Currently the feature provided in OAK-9208 emits WARNs like the following
{code}
5.02.2024 11:46:49.748 *WARN* [ResourceResolverFactory registration]
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$ChangeReporter
Unexpected changes (38) performed on a non-default mount. Printing at most
50_- /apps : Changed_-
java.lang.RuntimeException: null
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$CountingDiff.report(NonDefaultMountWriteReportingObserver.java:106)
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver.contentChanged(NonDefaultMountWriteReportingObserver.java:88)
at
org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:51)
at
org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:79)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler$ObservableLockBasedScheduler.contentChanged(LockBasedScheduler.java:394)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.execute(LockBasedScheduler.java:303)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.schedule(LockBasedScheduler.java:270)
at
org.apache.jackrabbit.oak.segment.SegmentNodeStore.merge(SegmentNodeStore.java:211)
at
org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:262)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate$WorkspaceCopy.perform(WorkspaceDelegate.java:130)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate.copy(WorkspaceDelegate.java:99)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl$2.performVoid(WorkspaceImpl.java:163)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:299)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:150)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:132)
at
.
{code}
It would be useful to add a dedicated exception message to the throwable (or
prevent logging it) and indicate that this only indicates where the JCR session
has been committed.
was:
Currently the feature provided in OAK-9208 emits WARNs like the following
{code}
5.02.2024 11:46:49.748 *WARN* [ResourceResolverFactory registration]
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$ChangeReporter
Unexpected changes (38) performed on a non-default mount. Printing at most
50_- /apps : Changed_-
java.lang.RuntimeException: null
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$CountingDiff.report(NonDefaultMountWriteReportingObserver.java:106)
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver.contentChanged(NonDefaultMountWriteReportingObserver.java:88)
at
org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:51)
at
org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:79)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler$ObservableLockBasedScheduler.contentChanged(LockBasedScheduler.java:394)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.execute(LockBasedScheduler.java:303)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.schedule(LockBasedScheduler.java:270)
at
org.apache.jackrabbit.oak.segment.SegmentNodeStore.merge(SegmentNodeStore.java:211)
at
org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:262)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate$WorkspaceCopy.perform(WorkspaceDelegate.java:130)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate.copy(WorkspaceDelegate.java:99)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl$2.performVoid(WorkspaceImpl.java:163)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:299)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:150)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:132)
at
biz.netcentric.cq.tools.actool.startuphook.impl.AcToolStartupHookServiceImpl.copyAcHistoryToOrFromApps(AcToolStartupHookServiceImpl.java:194)
at
biz.netcentric.cq.tools.actool.startuphook.impl.AcToolStartupHookServiceImpl.runAcTool(AcToolStartupHookServiceImpl.java:109)
at
[jira] [Created] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount
Konrad Windszus created OAK-10655:
-
Summary: Improve warning emitted for Unexpected changes performed
on a non-default mount
Key: OAK-10655
URL: https://issues.apache.org/jira/browse/OAK-10655
Project: Jackrabbit Oak
Issue Type: Improvement
Reporter: Konrad Windszus
Currently the feature provided in OAK-9208 emits WARNs like the following
{code}
5.02.2024 11:46:49.748 *WARN* [ResourceResolverFactory registration]
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$ChangeReporter
Unexpected changes (38) performed on a non-default mount. Printing at most
50_- /apps : Changed_-
java.lang.RuntimeException: null
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$CountingDiff.report(NonDefaultMountWriteReportingObserver.java:106)
at
org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver.contentChanged(NonDefaultMountWriteReportingObserver.java:88)
at
org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:51)
at
org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:79)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler$ObservableLockBasedScheduler.contentChanged(LockBasedScheduler.java:394)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.execute(LockBasedScheduler.java:303)
at
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.schedule(LockBasedScheduler.java:270)
at
org.apache.jackrabbit.oak.segment.SegmentNodeStore.merge(SegmentNodeStore.java:211)
at
org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:262)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate$WorkspaceCopy.perform(WorkspaceDelegate.java:130)
at
org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate.copy(WorkspaceDelegate.java:99)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl$2.performVoid(WorkspaceImpl.java:163)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:299)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:150)
at
org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:132)
at
biz.netcentric.cq.tools.actool.startuphook.impl.AcToolStartupHookServiceImpl.copyAcHistoryToOrFromApps(AcToolStartupHookServiceImpl.java:194)
at
biz.netcentric.cq.tools.actool.startuphook.impl.AcToolStartupHookServiceImpl.runAcTool(AcToolStartupHookServiceImpl.java:109)
at
biz.netcentric.cq.tools.actool.startuphook.impl.AcToolStartupHookServiceImpl.activate(AcToolStartupHookServiceImpl.java:94)
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.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:245)
at
org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
at
org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:687)
at
org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:531)
at
org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:317)
at
org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:307)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:354)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:1002)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:975)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:785)
at
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1274)
at
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1225)
at
org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1232)
at
org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1152)
at
[jira] [Commented] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
[ https://issues.apache.org/jira/browse/OAK-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817725#comment-17817725 ] Hudson commented on OAK-10654: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1364|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1364/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1364/console] > Build Jackrabbit/jackrabbit-oak-trunk #1363 failed > -- > > Key: OAK-10654 > URL: https://issues.apache.org/jira/browse/OAK-10654 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10649) MemoryDS: add toggle to limit document size
[ https://issues.apache.org/jira/browse/OAK-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817707#comment-17817707 ] Julian Reschke commented on OAK-10649: -- trunk: [03e307d7c5|https://github.com/apache/jackrabbit-oak/commit/03e307d7c5a295efb9a9f9192de9cb7b5b70519b] > MemoryDS: add toggle to limit document size > --- > > Key: OAK-10649 > URL: https://issues.apache.org/jira/browse/OAK-10649 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > > To simplify testing related to MongoDB's 16 MB limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10649) MemoryDS: add toggle to limit document size
[ https://issues.apache.org/jira/browse/OAK-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10649. -- Fix Version/s: 1.62.0 Resolution: Fixed > MemoryDS: add toggle to limit document size > --- > > Key: OAK-10649 > URL: https://issues.apache.org/jira/browse/OAK-10649 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.62.0 > > > To simplify testing related to MongoDB's 16 MB limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10649) MemoryDS: add toggle to limit document size
[ https://issues.apache.org/jira/browse/OAK-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10649: - Labels: candidate_oak_1_22 (was: ) > MemoryDS: add toggle to limit document size > --- > > Key: OAK-10649 > URL: https://issues.apache.org/jira/browse/OAK-10649 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > > To simplify testing related to MongoDB's 16 MB limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
Hudson created OAK-10654: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1363 failed Key: OAK-10654 URL: https://issues.apache.org/jira/browse/OAK-10654 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10653) BasicDocumentStore: handle DocumentStoreException on ds.create
[ https://issues.apache.org/jira/browse/OAK-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817684#comment-17817684 ] Julian Reschke commented on OAK-10653: -- trunk: [4a9219f4be|https://github.com/apache/jackrabbit-oak-/commit/4a9219f4be079f191ba486649514b3852f4005a2] > BasicDocumentStore: handle DocumentStoreException on ds.create > -- > > Key: OAK-10653 > URL: https://issues.apache.org/jira/browse/OAK-10653 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10653) BasicDocumentStore: handle DocumentStoreException on ds.create
[ https://issues.apache.org/jira/browse/OAK-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10653. -- Fix Version/s: 1.62.0 Resolution: Fixed > BasicDocumentStore: handle DocumentStoreException on ds.create > -- > > Key: OAK-10653 > URL: https://issues.apache.org/jira/browse/OAK-10653 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10653) BasicDocumentStore: handle DocumentStoreException on ds.create
[ https://issues.apache.org/jira/browse/OAK-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10653: - Labels: candidate_oak_1_22 (was: ) > BasicDocumentStore: handle DocumentStoreException on ds.create > -- > > Key: OAK-10653 > URL: https://issues.apache.org/jira/browse/OAK-10653 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10653) BasicDocumentStore: handle DocumentStoreException on ds.create
Julian Reschke created OAK-10653: Summary: BasicDocumentStore: handle DocumentStoreException on ds.create Key: OAK-10653 URL: https://issues.apache.org/jira/browse/OAK-10653 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk, test Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10652) Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store
[ https://issues.apache.org/jira/browse/OAK-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miroslav Smiljanic updated OAK-10652: - Affects Version/s: 1.60.0 > Repository writes in SegmentStoreMigrator blocked when migrating to Azure > segment store > --- > > Key: OAK-10652 > URL: https://issues.apache.org/jira/browse/OAK-10652 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-azure >Affects Versions: 1.60.0 >Reporter: Miroslav Smiljanic >Assignee: Miroslav Smiljanic >Priority: Major > > SegmentStoreMigrator is not using FileStore, where the repository lock is > usually obtained and writes allowed by calling > WriteAccessController#enableWriting. Instead, archive manager is used > directly, and repo writes are never enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10652) Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store
[ https://issues.apache.org/jira/browse/OAK-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miroslav Smiljanic updated OAK-10652: - Description: SegmentStoreMigrator is not using FileStore, where the repository lock is usually obtained and writes allowed by calling WriteAccessController#enableWriting. Instead, archive manager is used directly, and repo writes are never enabled. was: SegmentStoreMigrator is not using FileStore, where the repository lock is usually obtained and writes allowed by calling WriteAccessController#enableWriting. Instead, archive manager is used directly, and repo writes are never enabled. It was not discovered during the development of OAK-10006, because SegmentStoreMigrator does not have proper test coverage. > Repository writes in SegmentStoreMigrator blocked when migrating to Azure > segment store > --- > > Key: OAK-10652 > URL: https://issues.apache.org/jira/browse/OAK-10652 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-azure >Reporter: Miroslav Smiljanic >Assignee: Miroslav Smiljanic >Priority: Major > > SegmentStoreMigrator is not using FileStore, where the repository lock is > usually obtained and writes allowed by calling > WriteAccessController#enableWriting. Instead, archive manager is used > directly, and repo writes are never enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10652) Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store
Miroslav Smiljanic created OAK-10652: Summary: Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store Key: OAK-10652 URL: https://issues.apache.org/jira/browse/OAK-10652 Project: Jackrabbit Oak Issue Type: Bug Components: segment-azure Reporter: Miroslav Smiljanic Assignee: Miroslav Smiljanic SegmentStoreMigrator is not using FileStore, where the repository lock is usually obtained and writes allowed by calling WriteAccessController#enableWriting. Instead, archive manager is used directly, and repo writes are never enabled. It was not discovered during the development of OAK-10006, because SegmentStoreMigrator does not have proper test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
