Project

Profile

Help

Issue #4251

closed

Hard-Coded timeout causing issues with search on RHCC

Added by jmontleo@redhat.com about 6 years ago. Updated over 5 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Crane:
master
Platform Release:
Target Release - Crane:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Ansible Service Broker (a.k.a Automation Broker) depends on being able to run a search query against RHCC. That search sometimes returns no results.

It sounds as though we're bumping up against a timeout that is hard coded:

"Upstream Crane has a hard-coded 1 second timeout for search. So, if Solr takes longer than 1 second to respond, Crane will return a 503 back to the client."

https://github.com/pulp/crane/blob/5a34c2980999012cded4c17105e9e4a515fc2308/crane/search/base.py#L101

Actions #1

Updated by peasters about 6 years ago

This is a duplicate of #3706

Actions #2

Updated by jmontleo@redhat.com about 6 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions #3

Updated by bmbouter over 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF