MongoMK failover behaviour.

2017-05-04 Thread Ian Boston
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 retries

Re: MongoMK failover behaviour.

2017-05-04 Thread Marcel Reutegger
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 lo

Re: MongoMK failover behaviour.

2017-05-04 Thread Ian Boston
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 repeatedly >> from the MongoDB

Re: MongoMK failover behaviour.

2017-05-04 Thread Marcel Reutegger
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.

2017-05-04 Thread Ian Boston
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 opening a new one ) ?

Re: MongoMK failover behaviour.

2017-05-04 Thread Marcel Reutegger
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 abl

Re: MongoMK failover behaviour.

2017-05-04 Thread Justin Edelson
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 > > primary results in rea

Re: MongoMK failover behaviour.

2017-05-05 Thread Stefan Egli
Hi, On 04/05/17 16:56, "Justin Edelson" wrote: >>Hmm, depending on the Oak version, this may also be caused by OAK-5528. >> The current fix versions are 1.4.15 and 1.6.0. >> > >Would this show up in thread dumps? Based on the description, it seems >like >it should. Not necessarily. In OAK-5528