[jira] [Commented] (OAK-10557) Build Jackrabbit/jackrabbit-oak-trunk #1281 failed
[ https://issues.apache.org/jira/browse/OAK-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788158#comment-17788158 ] Hudson commented on OAK-10557: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1282|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1282/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1282/console] > Build Jackrabbit/jackrabbit-oak-trunk #1281 failed > -- > > Key: OAK-10557 > URL: https://issues.apache.org/jira/browse/OAK-10557 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1281 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1281|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1281/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1281/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10557) Build Jackrabbit/jackrabbit-oak-trunk #1281 failed
Hudson created OAK-10557: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1281 failed Key: OAK-10557 URL: https://issues.apache.org/jira/browse/OAK-10557 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1281 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1281|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1281/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1281/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10542) resolution of _deleted value ignores split docs in certain cases
[ https://issues.apache.org/jira/browse/OAK-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved OAK-10542. --- Fix Version/s: 1.60.0 Resolution: Fixed > resolution of _deleted value ignores split docs in certain cases > > > Key: OAK-10542 > URL: https://issues.apache.org/jira/browse/OAK-10542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Major > Fix For: 1.60.0 > > > When a document grows too large, part of it is split into previous documents. > That can include revisions of the "_deleted" property. > When reading a node at a particular revision, it first checks whether a node > was deleted at that revision or not. That resolution first checks the > revisions of _deleted locally, i.e. in the main document. Two cases currently > exist: > # If it finds a value in the local _deleted map, it accepts that as the valid > one. > # If it doesn't find a value in the local _deleted map, it reads the _deleted > maps from any split documents and searches there for a valid value. > If there was a split of \_deleted however, the first case is not sufficient - > as that currently ignores split documents in that case, while the most recent > revision (for a particular read revision) _can_ be in a split doc, rather > than the main doc. This happens if the newer split revisions (of _deleted) > are from a different clusterId than older non-split revisions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10382) oak-run support for flatfile and fullgc
[ https://issues.apache.org/jira/browse/OAK-10382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788065#comment-17788065 ] Stefan Egli commented on OAK-10382: --- * PR for flatfile command in oak-run created : https://github.com/apache/jackrabbit-oak/pull/1223 > oak-run support for flatfile and fullgc > --- > > Key: OAK-10382 > URL: https://issues.apache.org/jira/browse/OAK-10382 > Project: Jackrabbit Oak > Issue Type: Task > Components: oak-run >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Major > > As a follow-up of OAK-10347 we need a wrapper of the SimpleFlatFileUtil - > plus (potentially) a full-gc command which runs a full round of detail gc (in > DocumentNodeStore that is) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9796) oak-segment-remote and oak-segment-aws Redis tests fail with ARM processor (Apple M1)
[ https://issues.apache.org/jira/browse/OAK-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-9796. --- Fix Version/s: 1.60.0 (was: 1.42.0) (was: 1.22.11) Resolution: Fixed Both PRs are now merged. Resolving this issue. > oak-segment-remote and oak-segment-aws Redis tests fail with ARM processor > (Apple M1) > - > > Key: OAK-9796 > URL: https://issues.apache.org/jira/browse/OAK-9796 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-aws >Reporter: Thomas Mueller >Priority: Major > Labels: arm > Fix For: 1.60.0 > > > I'm can't build oak-segment-remote with my new laptop (Apple M1 chip) due to > https://github.com/kstyrc/embedded-redis/issues/51 - looks like > https://github.com/kstyrc/embedded-redis is used, which uses an ancient > version of Redis. > There is a fork of https://github.com/kstyrc/embedded-redis that seems more > up-to-date: https://github.com/ozimov/embedded-redis. The last commit there > was in 2020. The issue https://github.com/kstyrc/embedded-redis/issues/51 was > fixed a bit later. So switching to that embedded Redis version doesn't > resolve the issue either. > If Redis isn't available, then the test shouldn't fail... instead, the test > should be skipped. this is what we do for mongodb: if it isn't available, > then those tests are not run. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10536) Build Jackrabbit/jackrabbit-oak-trunk #1257 failed
[ https://issues.apache.org/jira/browse/OAK-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787982#comment-17787982 ] Hudson commented on OAK-10536: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1280|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1280/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1280/console] > Build Jackrabbit/jackrabbit-oak-trunk #1257 failed > -- > > Key: OAK-10536 > URL: https://issues.apache.org/jira/browse/OAK-10536 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1257 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1257|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1257/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1257/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9796) oak-segment-remote and oak-segment-aws Redis tests fail with ARM processor (Apple M1)
[ https://issues.apache.org/jira/browse/OAK-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787951#comment-17787951 ] Marcel Reutegger commented on OAK-9796: --- Merged [#1218|https://github.com/apache/jackrabbit-oak/pull/1218]. Created a new PR that skips the test if Redis cannot be started: https://github.com/apache/jackrabbit-oak/pull/1221 > oak-segment-remote and oak-segment-aws Redis tests fail with ARM processor > (Apple M1) > - > > Key: OAK-9796 > URL: https://issues.apache.org/jira/browse/OAK-9796 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-aws >Reporter: Thomas Mueller >Priority: Major > Labels: arm > Fix For: 1.42.0, 1.22.11 > > > I'm can't build oak-segment-remote with my new laptop (Apple M1 chip) due to > https://github.com/kstyrc/embedded-redis/issues/51 - looks like > https://github.com/kstyrc/embedded-redis is used, which uses an ancient > version of Redis. > There is a fork of https://github.com/kstyrc/embedded-redis that seems more > up-to-date: https://github.com/ozimov/embedded-redis. The last commit there > was in 2020. The issue https://github.com/kstyrc/embedded-redis/issues/51 was > fixed a bit later. So switching to that embedded Redis version doesn't > resolve the issue either. > If Redis isn't available, then the test shouldn't fail... instead, the test > should be skipped. this is what we do for mongodb: if it isn't available, > then those tests are not run. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10549) Improve performance of facet count at scale (Lucene)
[ https://issues.apache.org/jira/browse/OAK-10549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787939#comment-17787939 ] Thomas Mueller commented on OAK-10549: -- To avoid OOME when running the tests, I changed the test case to use only 10 facets: https://github.com/apache/jackrabbit-oak/commit/79ac7fd718b1abb495635cec38f9887a4a2b9219 With 200 facets, the test required 190 MB (-mx190m); with 10 facets, only 25 MB. > Improve performance of facet count at scale (Lucene) > > > Key: OAK-10549 > URL: https://issues.apache.org/jira/browse/OAK-10549 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.60.0 > > > Currently, reading many facets (eg. 20) at a time is quite slow when using a > Lucene index. We already cache the data, but performance is not all that > great. One of the reasons is that we run one Lucene query per facet column. > It is possible to speed this up, using eager facet caching. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10555) Bump elasticsearch version to 8.11.1
[ https://issues.apache.org/jira/browse/OAK-10555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-10555. Fix Version/s: 1.60.0 Resolution: Fixed > Bump elasticsearch version to 8.11.1 > > > Key: OAK-10555 > URL: https://issues.apache.org/jira/browse/OAK-10555 > Project: Jackrabbit Oak > Issue Type: Task > Components: search, search-elastic >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10541) Pipelined strategy: improve memory management of transform stage
[ https://issues.apache.org/jira/browse/OAK-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787900#comment-17787900 ] Julian Reschke edited comment on OAK-10541 at 11/20/23 9:55 AM: trunk: [dc6de0138e|https://github.com/apache/jackrabbit-oak/commit/dc6de0138ef94b2201cc72b5ce5d3d9972971037] [8494c94520|https://github.com/apache/jackrabbit-oak/commit/8494c94520e92374d658ca697f43daca26f61478] was (Author: reschke): trunk: [8494c94520|https://github.com/apache/jackrabbit-oak/commit/8494c94520e92374d658ca697f43daca26f61478] > Pipelined strategy: improve memory management of transform stage > > > Key: OAK-10541 > URL: https://issues.apache.org/jira/browse/OAK-10541 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Assignee: Julian Reschke >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10541) Pipelined strategy: improve memory management of transform stage
[ https://issues.apache.org/jira/browse/OAK-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787900#comment-17787900 ] Julian Reschke commented on OAK-10541: -- trunk: [8494c94520|https://github.com/apache/jackrabbit-oak/commit/8494c94520e92374d658ca697f43daca26f61478] > Pipelined strategy: improve memory management of transform stage > > > Key: OAK-10541 > URL: https://issues.apache.org/jira/browse/OAK-10541 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Assignee: Julian Reschke >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OAK-10541) Pipelined strategy: improve memory management of transform stage
[
https://issues.apache.org/jira/browse/OAK-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reopened OAK-10541:
--
Assignee: Julian Reschke
The change unfortunately bumped the package version for commons.sort to 2.0.0,
wich AFAIU is unnecessary:
{{[WARNING] org.apache.jackrabbit.oak.commons.sort: Excessive version increase;
detected 2.0.0, suggested 1.3.0}}
> Pipelined strategy: improve memory management of transform stage
>
>
> Key: OAK-10541
> URL: https://issues.apache.org/jira/browse/OAK-10541
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.60.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
