Failure in Tar MK failover test
Running org.apache.jackrabbit.oak.plugins.segment.failover.MBeanTest
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.861
sec FAILURE!
testClientAndServerEmptyConfig(org.apache.jackrabbit.oak.plugins.segment.failover.MBeanTest)
Time elapsed:
Hi,
In addition or instead of using the BlobStore, we could store the Lucene
index to the filesystem (persistence = file, path = ...).
But I would probably only do that on a case-by-case basis. I think it
would reduce, but not solve the compaction problem. Some numbers from a
test repository I
I have updated OAK-2082 with test run results. Looking at the result I
think FDS does provide a benefit in terms of lesser storage space.
Putting Lucene index on file system provides best storage efficiency
but then it would not work once we have TarMK failover implemented.
Chetan Mehrotra
On
Hi,I'm working on the TarMK failover package and trying to make it more robust and reliable. I noticed that there are still some situations in which the current implementation will run into persistent problems. It's not obvious what the "right" strategy is so let me paint the picture quite
Hi,
I agree with the FileStoreCorruptException idea. The change helps clarify
the problem (missing segment) and will not affect any existing code.
best,
alex
On Tue, Sep 9, 2014 at 2:25 PM, Martin Böttcher
martin.boettc...@greenbytes.de wrote:
Hi,
I'm working on the TarMK failover
Hi,
I noticed that running the same code (inside a test case) leads to different
results depending on how the test is started. The code:
---
NodeStore store = new SegmentNodeStore(storeS);
NodeBuilder rootbuilder = store.getRoot().builder();
NodeBuilder b = rootbuilder.child(store);
NodeBuilder
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/506
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason: scheduler
Build Source
Hi,
with maven we set a custom -Dupdate.limit=100
The default for the SegmentNodeBuilder is 1. Maybe this
is causing different segment sizes?
Regards
Marcel
On 09/09/14 16:27, Martin Böttcher martin.boettc...@greenbytes.de
wrote:
Hi,
I'm not sure what the execution mode is. In IntelliJ
