Hi, On 4 May 2017 at 15:19, Marcel Reutegger <[email protected]> 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 ) ? >> > > Yes, the MongoDB Java driver automatically routes queries based on their > required read preference. The failover is automatic and the driver should > direct queries to the new primary once available. Connection pooling is > done by the driver. Oak does not manage those. > Thanks. 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 able to write. All that points to the MongoDB driver config, or the MongoDB instances and not Oak. Best Regards Ian > > Regards > Marcel >
