Try setting file-log-level=debug and then monitor the logs, to see if there is any evidence of retries. The observed performance problem may turn out to be unrelated to this retry timeout after all. But since it happens under load, deadlock detection is a pretty strong candidate. If so the debug-level XDMP-DEADLOCK messages should give you enough information to solve the problem.
-- Mike > On 16 Feb 2015, at 09:01 , Muth, John, Springer UK <[email protected]> > wrote: > > Hello all, > > Recently while investigating poor performance under load we've been confused > by the presence of some requests/threads/queries staying around longer than > we thought should be possible. > > We have the following app server config settings: > 'default time limit' = 5 > 'max time limit' = 60 > > But we were often seeing the oldest requests of 185 seconds. > > Then we noticed in our 'Groups/Default' configuration there is a setting > 'retry timeout' set to what I assume is the default of 180. > > I'm guessing 5 + 180 = this 'retry timeout' setting is somehow playing a role > in those long-running requests. > > What is the purpose of the 'retry timeout' setting? > What kinds of problems would cause requests to be retried? > Should we expect the group-level 'retry timeout' setting to have precedence > over the app-server-specific settings time limit settings? > > Thanks for any advice, > John > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
