Closed Bug 719163 Opened 14 years ago Closed 13 years ago

Set the memcache progress key when indexing elastic from commandline

Categories

(support.mozilla.org :: Search, defect)

Product:
support.mozilla.org
Component:
Search
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
2012Q1

People

(Reporter: erik, Assigned: willkg)

Details

(Whiteboard: u=dev c=search s= p=1)

When reindexing is kicked off via /admin/search, that page shows a progress bar and doesn't let you start another indexing run. However, the page doesn't get clued in when the indexing run is started via manage.py esreindex. We should move the memcache diddling into es_reindex_with_progress() (which is the bottom-level routine) or someplace so we can't accidentally start 2 parallel indexing runs (which shouldn't hurt anything but would waste time).
Tossing this in the 2012.3 sprint.
Whiteboard: u=dev c=search s=2012.3 p=
Whiteboard: u=dev c=search s=2012.3 p= → u=dev c=search s=2012.4 p=
This should be pretty easy to do. Grabbing it and making it a 1pter.
Assignee: nobody → willkg
Whiteboard: u=dev c=search s=2012.4 p= → u=dev c=search s=2012.4 p=1
Whiteboard: u=dev c=search s=2012.4 p=1 → u=dev c=search s= p=1
I've changed my mind. For completeness sake this is interesting. Otherwise the only time someone would bump into this is if they're indexing from the command line and the search admin at the same time. That's kind of silly. Marking as WONTFIX.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.