Is it possible that there’s a synchronisation deadlock ? The tablets try to synchronize mulitple program stage instances but linked to the same tracked entity instance ?
or does the user have too much “trackentityinstances” ?
the “updates” and “inserts” of trackedentityinstance seem to last way too long and seem to deadlock
all connections are taken in the datasource pool and finally kill dhis2.
note that some threads stack traces looks similar to the “caffeine”
Is there a way to get more info in the logs ?
eg number of program stage/trackentity instances or payload posted ?
the nginx logs don’t say much
/var/log/nginx/error.log:2019/08/13 06:06:41 [error] 5052#0: *87 upstream timed out (110: Connection timed out) while reading response header from upstream, client: ...., server: , request: "POST /api/trackedEntityInstances?strategy=SYNC HTTP/1.1", upstream: "http://18.104.22.168:8080/api/trackedEntityInstances?strategy=SYNC", host: ...