Thanks, Vikas. >> Is it possible for you to set up session/cookie based load balancer?
This is probably possible, but before going through the trouble, I want to confirm that the behavior I described is by design (I hope not). I.e. does Jackrabbit Oak explicitly provides no guarantee on when the data is available in multi-instance cluster? On Thu, Feb 23, 2017 at 9:29 AM, Vikas Saurabh <[email protected]> wrote: > > We currently found a dirty workaround by > > running DocumentNodewStore.runBackgroundOperations() on every new > Session - > > but this does seem like an intended way to work in a cluster. > > > Yes, that definitely is a bad idea - I don't recall the exact details > atm, but I think background operations take exclusive locks so it'd > drop concurrent access performance a lot. Moreover, I don't think > background operations are supposed to be run concurrently - so, there > might be other issue too. > > > HTTP servers are load balanced. > > > Is it possible for you to set up session/cookie based load balancer? > For example the dispatcher (in AEM setups) sets up a rendid cookie so > that related requests are sent same AEM instance. > > Thanks, > Vikas > -- Thanks, Eugene
