Timeout on Terms in Several Plans

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
elasticsearch, python
Domain
backend, search

Research direction

Start at the search entry point and trace how terms matching several plans are sent to Elasticsearch; the issue gives “water” as an example and reports a 30-second read timeout. Reproduce the search and inspect the query and result handling. Done means searches across several plans complete without the reported timeout.

Written by the indexing model from the issue text.

Description

In search terms that appear in several plans, we often run into an ElasticSearch timeout. For instance, when searching for "water" we get:

elasticsearch.exceptions.ConnectionTimeout: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host='localhost', port=9200): Read timed out. (read timeout=30))

Dominant language
Python
Stars
2
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ucdavis/General-Plan-Map-Python

All issues in ucdavis/General-Plan-Map-Python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.