Hi, On 4 May 2017 at 11:26, Marcel Reutegger <mreut...@adobe.com> 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 primary and after 60s or more reports the Oak Discovery >> lease has been lost, resulting in many minutes of retries there eventually >> shutting down the repository. >> >> I don't currently have the MongoDB logs to share. Just wondering what to >> expect at this stage ? >> > > Oak will stop the oak-core bundle if a MongoDB primary is unavailable for > more than 110 seconds. The 110 seconds are based on the 120 seconds lease > timeout and a lease update interval of 10 seconds. > Yes, that happens after 120s. 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 ) ? Best Regards Ian > > When this happens, all reads and writes to the repository will fail. > Though, in an OSGi environment services depending on oak-core should stop > as well. You will need to restart the system or affected bundles once the > primary is available again. See also discussion in OAK-3397 and OAK-3250. > > Regards > Marcel >
