937174 - Silence flood of ElasticHttpNotFoundErrors during page move

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: General, defect)

Description

[Les Orchard [:lorchard]]

What did you do?
================
I moved a few hundred pages


What happened?
==============
The logs were flooded with errors like this:

[2013-11-11 08:42:20,214: ERROR/MainProcess] Task elasticutils.contrib.django.tasks.unindex_objects[393dc304-f68e-42fd-b7bf-cab1a2
6d6339] raised exception: ElasticHttpNotFoundError(404, {u'_type': u'wiki_document', u'ok': True, u'_index': u'mdn-main_index', u'
_version': 2, u'found': False, u'_id': u'69229'})
Traceback (most recent call last):
  File "/home/vagrant/src/vendor/packages/celery/celery/execute/trace.py", line 181, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/home/vagrant/src/vendor/src/elasticutils/elasticutils/contrib/django/tasks.py", line 81, in unindex_objects
    mapping_type.unindex(id_)
  File "/home/vagrant/src/vendor/src/elasticutils/elasticutils/__init__.py", line 2055, in unindex
    es.delete(index, cls.get_mapping_type_name(), id_)
  File "/home/vagrant/src/vendor/src/pyelasticsearch/pyelasticsearch/client.py", line 96, in decorate
    return func(*args, query_params=query_params, **kwargs)
  File "/home/vagrant/src/vendor/src/pyelasticsearch/pyelasticsearch/client.py", line 411, in delete
    query_params=query_params)
  File "/home/vagrant/src/vendor/src/pyelasticsearch/pyelasticsearch/client.py", line 254, in send_request
    self._raise_exception(resp, prepped_response)
  File "/home/vagrant/src/vendor/src/pyelasticsearch/pyelasticsearch/client.py", line 269, in _raise_exception
    raise error_class(response.status_code, error_message)
ElasticHttpNotFoundError: (404, {u'_type': u'wiki_document', u'ok': True, u'_index': u'mdn-main_index', u'_version': 2, u'found':
False, u'_id': u'69229'})

What should have happened?
==========================
No such errors.

Is there anything else we should know?
======================================
These errors occur during page deletion and subsequent removal from the search index. But, I don't think these particular pages were ever in the search index, and so we get 404 errors. 

That's fine, but we should probably just catch them in the unindex task and squelch them

Comment 1

[Les Orchard [:lorchard]]

Note that these errors are also flooding into email inboxes as server errors. I think they're ultimately harmless.

Comment 2

[Les Orchard [:lorchard]]

Also: https://errormill.mozilla.org/mdn/mdn-stage/group/127252/

Comment 3

[Les Orchard [:lorchard]]

Also also: https://errormill.mozilla.org/mdn/mdn-dev/group/127227/

Comment 4

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.