Hi, Unfortunately everyone has a different requirement for the maximum time allowed before timing out. But obviously you would want to measure how long your individual authorities take to resolve a user, and base it on that.
Karl On Fri, Jun 12, 2015 at 2:10 AM, <[email protected]> wrote: > Hi, > > even this was not the initial issue. Your suggestion to set the socket > timeout for the Solr search component is a important point in order to > decouple the dependency between search and authority. > > Optimally we would configure the timeout as short as possible but long > enough. > > Do you or anybody else have best practices setting the timeout. What's a > good default? > > best > -Rüdiger > > > Zitat von Karl Wright <[email protected]>: > > I believe you can set the socket timeout for the Solr plugin via plugin >> parameters. I suggest you try that to limit the damage you'd get if the >> request could not be completed. >> >> Thanks, >> Karl >> >> >> On Thu, Jun 11, 2015 at 9:13 AM, <[email protected]> wrote: >> >> >>> Hi there, >>> >>> we have the following situation ... >>> >>> When one of the configured authority connections does not get a response >>> from its service URL, the search results in a response with an error >>> (status 503). >>> >>> What's hppening in the background: >>> The service URL is not reachable, being blocked by a firewall. At client >>> side: The Solr-XHR request is pending for long time and finally results >>> in >>> a 503. >>> >>> The expected behavior would be, that the search is still working and does >>> not show results that are protected by this authority connection but >>> anything else. >>> >>> Currently we are starting our analysis. So far I'm interessted if this >>> situation is known by anybody out there and or if there are any hints or >>> ideas to keep the serach alive even an authority connection is not >>> available at search execution time. >>> >>> Thanks in advance >>> -Rüdiger >>> >>> >>> > > >
