elastic-recheck/elastic_recheck
Clark Boylan 02d0651f29 Better event checking timeouts
Previously we gave every event a 20 minute timeout. This meant that we
could eventually rollover on the day and start querying against current
indexes for data in older indexes. If this happens every query would
fail because we are looking in the wrong index. Every query failing
means we run the 20 minute timeout every time.

All this results in snowballing never being able to check if events are
indexed.

Address this by using the gerrit eventCreatedOn timestamp to determine
when our timeout is hit. We will timeout 20 minutes from that timestamp
regardless of how long interim processing has taken us. This should over
longer periods of time ensure we query the current index for current
events.

Change-Id: Ic9ed7fefae37d2668de5d89e0d06b8326eadfbb9
2018-11-30 19:34:54 +00:00
..
cmd Made elastic-recheck py3 compatible 2018-11-29 20:15:07 +00:00
tests Better event checking timeouts 2018-11-30 19:34:54 +00:00
__init__.py Further shuffling to get this to fit the standard code layout 2013-09-25 18:20:51 -07:00
bot.py Made elastic-recheck py3 compatible 2018-11-29 20:15:07 +00:00
config.py Made elastic-recheck py3 compatible 2018-11-29 20:15:07 +00:00
elasticRecheck.py Better event checking timeouts 2018-11-30 19:34:54 +00:00
loader.py Add allow-nonvoting key 2016-02-01 07:55:30 -08:00
log.py Make Elastic Recheck Watch more reusable 2016-09-20 18:11:30 -07:00
query_builder.py Fix query_builder.result_ready() query for zuulv3 results 2018-05-08 17:57:42 -04:00
results.py Wait until the most recent index is available 2016-10-20 10:48:55 -07:00