Closed
Bug 715926
Opened 12 years ago
Closed 12 years ago
Make ES timeout configurable for indexing
Categories
(support.mozilla.org :: Search, defect)
support.mozilla.org
Search
Tracking
(Not tracked)
VERIFIED
FIXED
2012-01-24
People
(Reporter: jsocol, Unassigned)
References
Details
(Whiteboard: u=dev c=search s=2012.1 p=1 post-sprint [qa-])
Right now we have ES_TIMEOUT but it doesn't apply to the indexing step. We should either add another setting or make this one also apply to indexing. I could see adding another setting because PUT requests might, on average, take a lot longer than GET, but I don't really know.
Comment 1•12 years ago
|
||
Indexing happens in tasks or a cron job--so it doesn't affect http requests. Given that, I'd be game for a ES_INDEXING_TIMEOUT and if it's not defined, default to ES_TIMEOUT. If you're ok with that, I'll throw it together now with docs.
Comment 2•12 years ago
|
||
http://elasticsearch-users.115913.n3.nabble.com/Timing-out-while-indexing-td2992500.html Putting that in here so we don't lose it somewhere. One thing it suggests is making your timeout much larger for indexing.
Comment 3•12 years ago
|
||
Making this depend on bug #709080 since that refactors the ES indexing code.
Depends on: 709080
Comment 4•12 years ago
|
||
This was done with bug #709080. Marking as FIXED and [qa-].
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: u=dev c=search s=2012.1 p=1 post-sprint [qa-]
Updated•12 years ago
|
Target Milestone: --- → 2012-01-24
You need to log in
before you can comment on or make changes to this bug.
Description
•