BUILD FAILURE: Jackrabbit Oak - Build # 253 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #253) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/253/ to view the results. Changes: [angela] OAK-5882 : Improve coverage for oak.security code in oak-core Test results: 1 tests

Re: MongoMK failover behaviour.

Hi, On Thu, May 4, 2017 at 10:46 AM Marcel Reutegger wrote: > Hi, > > On 04/05/17 16:35, Ian Boston wrote: > > Looks like there might be a problem with the MongoDB deployment in the > case > > I am looking at. Either due to performance or misconfiguration. Dropping > a > >

Re: MongoMK failover behaviour.

Hi, On 04/05/17 16:35, Ian Boston wrote: Looks like there might be a problem with the MongoDB deployment in the case I am looking at. Either due to performance or misconfiguration. Dropping a primary results in read queries failing and after 120s the Oak repositories shutdown as they are not

Re: MongoMK failover behaviour.

Hi, On 4 May 2017 at 15:19, Marcel Reutegger wrote: > Hi, > > On 04/05/17 14:57, Ian Boston wrote: > >> Before 120 seconds, should the MongoDB Java driver route read queries to a >> secondary and use the new primary without any action by Oak (eg closing a >> connection and

Re: MongoMK failover behaviour.

Hi, On 04/05/17 14:57, Ian Boston wrote: Before 120 seconds, should the MongoDB Java driver route read queries to a secondary and use the new primary without any action by Oak (eg closing a connection and opening a new one ) ? Yes, the MongoDB Java driver automatically routes queries based on

Re: MongoMK failover behaviour.

Hi, On 4 May 2017 at 11:26, Marcel Reutegger wrote: > Hi, > > On 04/05/17 12:02, Ian Boston wrote: > >> What is the expected behaviour when a Oak MongoMK experiences a MongoDB >> primary failure. >> >> I am looking at an instance that appears to try and retry reads

Re: Sort order in MongoMissingLastRevSeeker

On Thu, May 4, 2017 at 3:15 PM, Marcel Reutegger wrote: > A can't really think of a reason why the sort order must be descending in > MongoMissingLastRevSeeker. I also do not remember. I think it should be fine to drop the sort criteria. Chetan Mehrotra

Re: MongoMK failover behaviour.

Hi, On 04/05/17 12:02, Ian Boston wrote: What is the expected behaviour when a Oak MongoMK experiences a MongoDB primary failure. I am looking at an instance that appears to try and retry reads repeatedly from the MongoDB primary and after 60s or more reports the Oak Discovery lease has been

MongoMK failover behaviour.

Hi, What is the expected behaviour when a Oak MongoMK experiences a MongoDB primary failure. I am looking at an instance that appears to try and retry reads repeatedly from the MongoDB primary and after 60s or more reports the Oak Discovery lease has been lost, resulting in many minutes of

Sort order in MongoMissingLastRevSeeker

Hi, I recently noticed the sort order in MongoMissingLastRevSeeker on _modified. The query sorts descending. I think this may be a problem given the isolation guarantees provides by MongoDB. See also discussion in OAK-4535. In particular, I'm thinking of the following behaviour mentioned in

BUILD FAILURE: Jackrabbit Oak - Build # 246 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #246) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/246/ to view the results. Changes: [chetanm] OAK-5558 - Consistency checker for Lucene indexes Implemented support for testing based on