This is most likely due to rate at which event gets generated and thus causing Observation queue to fill up (1000 default size). If the backing JCR listener is slow in processing the queue would get filled and BackgroundObserver would start compacting/merging the diff thus converting local events to external.
There are two solutions 1. Throttle the commits - CommitRateLimiter 2. Have a non limiting queue - Then you end up with OOM if gap in processing rate is large Chetan Mehrotra On Thu, Jun 25, 2015 at 8:47 PM, Marius Petria <mpet...@adobe.com> wrote: > Hi, > > I understand that under high load local events can be reported as external. > My question is why does this happen also for tarmk, where there is a single > instance active (receiving external events on a single instance seems odd)? > Also, is there a way to disable this functionality, meaning on tarmk to > always receive the local events with their associated data (specifically the > userData)? > > Regards, > Marius >
