Closed
Bug 963311
Opened 12 years ago
Closed 12 years ago
Bug in bz_cache_refresh.py ?
Categories
(Tree Management Graveyard :: OrangeFactor, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bburton, Assigned: jgriffin)
References
Details
Attachments
(2 files)
|
150.21 KB,
text/plain
|
Details | |
|
1.61 KB,
patch
|
mcote
:
review+
|
Details | Diff | Splinter Review |
Earlier today the ES cluster in SCL3 which hosts the 'bzcache' index had some OOM issues that required a restart of the cluster
Unfortunately this seems to cause corruption of the 'bzcache' index
I reran the cronjob to recreate the index, after troubleshooting confirmed it was not recoverable from the cluster.
But during the cron job run, the ES cluster logged a couple errors, which may be a bug in the script or how it's making a query to ES, so I wanted to bring it to your attention
Attached is the log output from ES
| Assignee | ||
Comment 1•12 years ago
|
||
Thanks, it looks like we're trying to update bzcache with too many entries in one request. I'll make a fix for this.
Assignee: nobody → jgriffin
| Assignee | ||
Comment 2•12 years ago
|
||
ES seems to default to a limit of 1024 boolean clauses per search; this will cause us to request no more than 250 at once.
Attachment #8371145 -
Flags: review?(mcote)
Comment 3•12 years ago
|
||
Comment on attachment 8371145 [details] [diff] [review]
Request bugs from ES in chunks of 200,
Review of attachment 8371145 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good to me!
Attachment #8371145 -
Flags: review?(mcote) → review+
| Assignee | ||
Comment 4•12 years ago
|
||
| Assignee | ||
Comment 5•12 years ago
|
||
...and deployed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: Testing → Tree Management
Updated•5 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•