Re: [VOTE] Release Apache Jackrabbit Oak 1.7.11
[X] +1 Release this package as Apache Jackrabbit Oak 1.7.11 where [INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T22:39:06+03:00) [INFO] OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac" [INFO] Java version: 1.8.0_65, vendor: Oracle Corporation Andrei 2017-11-07 15:15 GMT+02:00 Davide Giannella: > Please vote on releasing this package as Apache Jackrabbit Oak 1.7.11. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.11 > [ ] -1 Do not release this package because... > > D. >
Re: [VOTE] Release Apache Jackrabbit Oak 1.7.11
[X] +1 Release this package as Apache Jackrabbit Oak 1.7.11 alex On Tue, Nov 7, 2017 at 2:15 PM, Davide Giannellawrote: > A candidate for the Jackrabbit Oak 1.7.11 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.11/ > > The release candidate is a zip archive of the sources in: > > > https://svn.apache.org/repos/asf/jackrabbit/oak/tags/ > jackrabbit-oak-1.7.11/ > > The SHA1 checksum of the archive is > 445beb053b7f11b65d31e85da777b8d45b44f747. > > A staged Maven repository is available for review at: > > https://repository.apache.org/ > > The command for running automated checks against this release candidate is: > > $ sh check-release.sh oak 1.7.11 > 445beb053b7f11b65d31e85da777b8d45b44f747 > > Please vote on releasing this package as Apache Jackrabbit Oak 1.7.11. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.11 > [ ] -1 Do not release this package because... > > D. >
BUILD FAILURE: Jackrabbit Oak - Build # 953 - Still Failing
The Apache Jenkins build system has built Jackrabbit Oak (build #953) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/953/ to view the results. Changes: [mreutegg] OAK-5028: Remove DocumentStore.update() Test results: 1 tests failed. FAILED: org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing[SegmentTar] Error Message: Just filled queue must not convert local->external expected:<6> but was:<4> Stack Trace: java.lang.AssertionError: Just filled queue must not convert local->external expected:<6> but was:<4> at org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:347)
Re: [VOTE] Release Apache Jackrabbit Oak 1.7.11
On 07/11/17 14:15, Davide Giannella wrote: Please vote on releasing this package as Apache Jackrabbit Oak 1.7.11. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. All checks OK. +1 Release this package as Apache Jackrabbit Oak 1.7.11 [INFO] Apache Maven 3.3.9 [INFO] OS name: "linux", version: "4.4.0-97-generic", arch: "amd64", family: "unix" [INFO] Java version: 1.8.0_151, vendor: Oracle Corporation Regards Marcel
BUILD FAILURE: Jackrabbit Oak - Build # 952 - Still Failing
The Apache Jenkins build system has built Jackrabbit Oak (build #952) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/952/ to view the results. Changes: [thomasm] OAK-301 Document Oak [davide] [maven-release-plugin] prepare for next development iteration [davide] [maven-release-plugin] prepare release jackrabbit-oak-1.7.11 [davide] Apache Jackrabbit Oak 1.7.11 wrong javadocs [davide] Apache Jackrabbit Oak 1.7.11 release notes [davide] Apache Jackrabbit Oak 1.7.11 missing licence header Test results: All tests passed
Re: [VOTE] Release Apache Jackrabbit Oak 1.7.11
On 2017-11-07 14:15, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.7.11 where: [INFO] Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00) [INFO] OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" [INFO] Java version: 9, vendor: Oracle Corporation Best regards, Julian
[VOTE] Release Apache Jackrabbit Oak 1.7.11
A candidate for the Jackrabbit Oak 1.7.11 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.11/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.11/ The SHA1 checksum of the archive is 445beb053b7f11b65d31e85da777b8d45b44f747. A staged Maven repository is available for review at: https://repository.apache.org/ The command for running automated checks against this release candidate is: $ sh check-release.sh oak 1.7.11 445beb053b7f11b65d31e85da777b8d45b44f747 Please vote on releasing this package as Apache Jackrabbit Oak 1.7.11. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.11 [ ] -1 Do not release this package because... D.
BUILD FAILURE: Jackrabbit Oak - Build # 951 - Failure
The Apache Jenkins build system has built Jackrabbit Oak (build #951) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/951/ to view the results. Changes: [frm] OAK-6896 - Log the initial size of the FileStore at startup [frm] OAK-6890 - Fix SafeRunnable rethrow policy SafeRunnable should never rethrow the Throwable it catches. While it might not make sense in some cases - e.g. OutOfMemoryError - it prevents the SafeRunnable from being unscheduled from the ScheduledExecutorService that runs it periodically. Each SafeRunnable represents a background task that is important for the health of the FileStore and should never be accidentally unscheduled. Test results: All tests passed
Re: garbage collector in mongo document node store
Hi Marco, On 05/11/17 18:37, Marco Piovesana wrote: I've seen that there are three types of garbage collectors: version, journal and blob. Do I have to call them all? No, you only have to take care of scheduling the Revision GC and the Blob GC. The Journal GC is scheduled automatically by the implementation. If yes, there's a specific order that I should keep? For my trial I did this: The Blob GC will potentially be able to remove more blobs when scheduled after the Revision GC. However, a common schedule I see is Revision GC once a day and Blob GC once a week (e.g. on the weekend). So it doesn't matter that much which one runs first. documentNodeStore.getVersionGarbageCollector().gc(1, TimeUnit.DAYS); This works, but I would recommend you use the RepositoryManagementMBean, which is considered public and stable, whereas the method you are using is considered internal and subject to change between releases. documentNodeStore.getJournalGarbageCollector().gc(1, TimeUnit.DAYS); As mentioned already, this is not necessary. long oneDay = TimeUnit.SECONDS.convert(1, TimeUnit.DAYS); documentNodeStore.createBlobGarbageCollector(oneDay, ClusterRepositoryInfo. getOrCreateId(documentNodeStore)).collectGarbage(false); My recommendation again is to use RepositoryManagementMBean. There's a startDataStoreGC() method. This avoids using implementation specific classes. Regards Marcel