Story #3706
closed
Crane's timeout for backend search requests is not configurable
0%
Description
Crane currently uses a hard-coded 1 second timeout when querying the GSA or Solr search backends. This timeout can be too short for some uses cases, like development environments where resources are constrained.
The timeout should be configurable in Crane's config file so administrators can choose an appropriate value.
Updated by CodeHeeler over 6 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Updated by mhrivnak over 6 years ago
- Tags Easy Fix added
+1. I originally made the timeout 1 second, likely for no particular reason other than optimism. This week it came back to bite me, just a little. :)
Testing another app against an internal "stage" deployment of crane, with a corresponding stage deployment of the search infra, crane was sometimes returning 500 responses to search requests. @peasters figured out it was the timeout, and that the stage solr instance wasn't able to respond in under 1 second until its cache had been sufficiently warmed. Hence after several 500 responses, it would start working.
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.