cache and index backup and restore ?
Hi, Having done a cold backup of a MongoMK instance with a FS Datastore, is there any advantage in also backing up the local disk copy of the lucene index (normally in repository/index/** ) and persistent cache file (repository/cache/**) so that it can be restored on more than one Oak instance in the cluster. or do both those subtrees get zapped when the new instance starts ? Also, if I tar up everything to restore multiple times, is there anything I need to edit on disk to make the instances distinct. IIRC there was a sling.id at one point, but that might have been JR2 rather than Oak. Best Regards Ian
[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 697 - Still Failing
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #697) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/697/ to view the results. Changes: [mduerig] OAK-3894 - Atomic counter documentation Missing license header [alexparvulescu] OAK-3904 Compaction Map predicate should use cached state for evaluation [frm] OAK-3862 - Move integration tests in a different Maven module [mreutegg] OAK-3903: Commit fails even though change made it to the DocumentStore Test results: 31 tests failed. FAILED: org.apache.jackrabbit.oak.plugins.segment.standby.ExternalSharedStoreIT.testProxyFlippedStartByte Error Message: expected:<{ root = { ... } }> but was:<{ root : { } }> Stack Trace: java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:191) at org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedStartByte(DataStoreTestBase.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) 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.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) FAILED: org.apache.jackrabbit.oak.api.ContentSessionTest.initializationError Error Message: org/apache/commons/lang/StringUtils Stack Trace: java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils at org.apache.jackrabbit.oak.fixture.DocumentRdbFixture.toString(DocumentRdbFixture.java:82) at java.text.MessageFormat.subformat(MessageFormat.java:1271) at java.text.MessageFormat.format(MessageFormat.java:860) at java.text.Format.format(Format.java:157) at java.text.MessageFormat.format(MessageFormat.java:836) at org.junit.runners.Parameterized.createTestWithParameters(Parameterized.java:347) at org.junit.runners.Parameterized.createTestWithNotNormalizedParameters(Parameterized.java:274) at org.junit.runners.Parameterized.createTestsForParameters(Parameterized.java:328) at
[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 696 - Still Failing
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #696) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/696/ to view the results. Changes: No changes Test results: All tests passed
Oak 1.4 roadmap
Hello everyone, as we're approaching to a year since we released Oak 1.2 here's a proposal of soft-dates for releasing 1.4. With soft-dates I mean they could shift a bit around depending on issue needs. The team already went through the exercise of scheduling what's not so important for 1.6. # Major Feature Freeze - 1st February - Oak 1.3.15 Progressive commit slow down and risk-control starting after 1.3.15 cut. # 1.4 Branching - 29th February - Oak 1.4.0 - Oak 1.5.0 Branching of 1.4, release 1.4.0, release 1.5.0. They should all be the same code from an Oak perspective. >From here on we'll resume the regular bi-weekly unstable cut (1.5.x) and a stable cut every 3 weeks (1.0, 1.2, 1.4). Cheers Davide
Re: cache and index backup and restore ?
Hi, Sure, there is a performance advantage (for both the persistent cache and the Lucene index cache). But how much exactly depends on the use case. You forgot the "persistent cache" by the way. When restoring, you need to ensure that the local cache is not newer than the remote (MongoDB), and from the same "branch" (when copying and branching MongoDB databases). > Also, if I tar up everything to restore multiple times, is there >anything I need to edit on disk to make the instances distinct. No, not that I know of. Regards, Thomas On 21/01/16 14:56, "ianbos...@gmail.com on behalf of Ian Boston"wrote: >Hi, >Having done a cold backup of a MongoMK instance with a FS Datastore, is >there any advantage in also backing up the local disk copy of the lucene >index (normally in repository/index/** ) and persistent cache file >(repository/cache/**) so that it can be restored on more than one Oak >instance in the cluster. or do both those subtrees get zapped when the >new instance starts ? > >Also, if I tar up everything to restore multiple times, is there anything >I >need to edit on disk to make the instances distinct. IIRC there was a >sling.id at one point, but that might have been JR2 rather than Oak. > >Best Regards >Ian
New Segment Store bundle
Hi all, I committed a big change in r1726048 because of OAK-3744. I had to move some code around and adjust some POMs and tests. Please let me know if something is broken for you. I did my best by running unit and integration tests on my machine before committing, but I can't guarantee a 100% success rate on every development machine out there. If something is broken, please reply to this email or create a new issue and assign it to me. Thanks, Francesco