Re: Oak 1.3.6 release plan

On 2015-09-14 10:17, Julian Reschke wrote: On 2015-09-14 10:03, Stefan Egli wrote: On 14/09/15 09:51, "Marcel Reutegger" wrote: ...would it make sense to just disable the lease check for the diagnostics in oak-run? ... +1 as a short-term fix Cheers, Stefan I agree

Re: Oak 1.3.6 release plan

As the 1.3.6 is already in the voting phase, it would mean -1 for that release - not sure if it's enough of an issue for that though? (mind you, the issue was already there in 1.3.5..) Cheers, Stefan On 14/09/15 12:29, "Julian Reschke" wrote: >On 2015-09-14 10:17, Julian

Re: Oak 1.3.6 release plan

On 2015-09-14 09:17, Marcel Reutegger wrote: Hi, are things really broken because of the LeaseCheckDocumentWrapper? AFAIU it means the DocumentNodeStore will currently fall back to a generic implementation for getReferencedBlobsIterator(), which works but may be less efficient than the Mongo

Re: Oak 1.3.6 release plan

Hi, I assume the second issue is: https://issues.apache.org/jira/browse/OAK-3389 please note, this is now a new problem. The instanceof check would fail already before when one of the other wrappers was enabled (logging or timing). Regards Marcel On 14/09/15 09:51, "Marcel Reutegger" wrote:

Re: Oak 1.3.6 release plan

Hi, are things really broken because of the LeaseCheckDocumentWrapper? AFAIU it means the DocumentNodeStore will currently fall back to a generic implementation for getReferencedBlobsIterator(), which works but may be less efficient than the Mongo custom implementation. Regards Marcel On

Re: Oak 1.3.6 release plan

Hi, On 14/09/15 09:42, "Julian Reschke" wrote: >On 2015-09-14 09:17, Marcel Reutegger wrote: >> are things really broken because of the LeaseCheckDocumentWrapper? >> AFAIU it means the DocumentNodeStore will currently fall back >> to a generic implementation for getReferencedBlobsIterator(), >>

Re: Oak 1.3.6 release plan

On 14/09/15 09:51, "Marcel Reutegger" wrote: >...would it >make sense to just disable the lease check for the diagnostics >in oak-run? ... +1 as a short-term fix Cheers, Stefan

Re: Oak 1.3.6 release plan

On 2015-09-14 10:03, Stefan Egli wrote: On 14/09/15 09:51, "Marcel Reutegger" wrote: ...would it make sense to just disable the lease check for the diagnostics in oak-run? ... +1 as a short-term fix Cheers, Stefan I agree that this would have been broken by the other

Re: Oak 1.3.6 release plan

On 11/09/2015 13:30, Julian Reschke wrote: > On 2015-09-10 09:19, Marcel Reutegger wrote: >> Hi, >> >> I plan to release 1.3.6 on Monday. And this time I really hope >> I will have the time to actually perform the release. Thanks >> Amit for taking care of the previous 1.3.5 release! >> ... > >

Re: Oak 1.3.6 release plan

On 2015-09-10 09:19, Marcel Reutegger wrote: Hi, I plan to release 1.3.6 on Monday. And this time I really hope I will have the time to actually perform the release. Thanks Amit for taking care of the previous 1.3.5 release! ... Given the amount of breakage we currently have because of

Oak 1.3.6 release plan

Hi, I plan to release 1.3.6 on Monday. And this time I really hope I will have the time to actually perform the release. Thanks Amit for taking care of the previous 1.3.5 release! We currently have 86 issues scheduled for the release [0]. This is roughly twice as many we had pending before the

Re: Oak 1.3.6 release plan

Hello, Can I ask some committer to merge two issues before the release? OAK-3148 Allows to migrate one blobstore to another during normal Oak operations. Already reviewed by the Thomas Mueller. OAK-2171 The command line interface for all the upgrade/sidegrade features in Oak with a bunch of