I am trying to configure ElasticSearch / Haystack in a local local environment (vagrant VM with Ubuntu 12.04) and I cannot process the reindexing process.
ES is running and I created a new index (I use elasticsearch-head to view the status of the index in the browser). I can create a new index and query it, so I know that ES is working.
My problem is with the Haystack rebuild_index :
(.venv) vagrant@precise32 :/app$ foreman run ./manage.py rebuild_index WARNING: This will irreparably remove EVERYTHING from your search index in connection 'default'. Your choices after this are to restore from backups or rebuild via the `rebuild_index` command. Are you sure you wish to continue? [y/N] y Removing all documents from your index because you said so. DEBUG Making a request equivalent to this: curl -XDELETE 'http://127.0.0.1:9200/test_app' -d '""' INFO Starting new HTTP connection (1): 127.0.0.1 DEBUG "DELETE /test_app HTTP/1.1" 200 31 DEBUG response status: 200 DEBUG got response {u'acknowledged': True, u'ok': True} DEBUG Making a request equivalent to this: curl -XPOST 'http://127.0.0.1:9200/test_app/_refresh' -d '""' DEBUG "POST /test_app/_refresh HTTP/1.1" 404 66 DEBUG response status: 404 Failed to clear Elasticsearch index: (404, u'IndexMissingException[[test_app] missing]') ERROR Failed to clear Elasticsearch index: (404, u'IndexMissingException[[test_app] missing]') All documents removed.
Looking at this loggging - it seems that Haystack is trying to update the index that he just deleted - which would always fail.
What am I doing wrong?
[UPDATE 1]
If I share POST requests, I can get this to run:
(.venv) vagrant@precise32 :/app$ curl -XPOST 'http://127.0.0.1:9200/test_app/' {"ok":true,"acknowledged":true} (.venv) vagrant@precise32 :/app$ curl -XPOST 'http://127.0.0.1:9200/test_app/_refresh' -d '""' {"ok":true,"_shards":{"total":10,"successful":5,"failed":0}}
[UPDATE 2]
Digging in the code, the basic ES method that is called when clear_index run:
def clear(self, models=[], commit=True): [...] if not models: self.conn.delete_index(self.index_name) else: [...] if commit: self.conn.refresh(index=self.index_name)
What looks wrong as it calls conn.refresh at the index that it just deleted?
[UPDATE 3]
I think that the above errors can be a red herring, as management teams will ignore the errors and continue, giving this error, which, I think, is more serious:
(.venv) vagrant@precise32 :/app$ foreman run ./manage.py update_index --verbosity=3 Skipping '<class 'django.contrib.auth.models.Permission'>' - no index. Skipping '<class 'django.contrib.auth.models.Group'>' - no index. Skipping '<class 'django.contrib.auth.models.User'>' - no index. Skipping '<class 'django.contrib.contenttypes.models.ContentType'>' - no index. Skipping '<class 'django.contrib.sessions.models.Session'>' - no index. Skipping '<class 'django.contrib.sites.models.Site'>' - no index. Skipping '<class 'django.contrib.admin.models.LogEntry'>' - no index. Skipping '<class 'django.contrib.flatpages.models.FlatPage'>' - no index. ERROR Error updating test_app using default Traceback (most recent call last): File "/home/vagrant/.venv/src/django-haystack/haystack/management/commands/update_index.py", line 210, in handle_label self.update_backend(label, using) File "/home/vagrant/.venv/src/django-haystack/haystack/management/commands/update_index.py", line 239, in update_backend end_date=self.end_date) File "/home/vagrant/.venv/src/django-haystack/haystack/indexes.py", line 157, in build_queryset index_qs = self.index_queryset(using=using) TypeError: index_queryset() got an unexpected keyword argument 'using' Traceback (most recent call last): File "./manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/home/vagrant/.venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/home/vagrant/.venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/vagrant/.venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/home/vagrant/.venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/home/vagrant/.venv/src/django-haystack/haystack/management/commands/update_index.py", line 184, in handle return super(Command, self).handle(*items, **options) File "/home/vagrant/.venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 341, in handle label_output = self.handle_label(label, **options) File "/home/vagrant/.venv/src/django-haystack/haystack/management/commands/update_index.py", line 210, in handle_label self.update_backend(label, using) File "/home/vagrant/.venv/src/django-haystack/haystack/management/commands/update_index.py", line 239, in update_backend end_date=self.end_date) File "/home/vagrant/.venv/src/django-haystack/haystack/indexes.py", line 157, in build_queryset index_qs = self.index_queryset(using=using) TypeError: index_queryset() got an unexpected keyword argument 'using'
[UPDATE 4]
OK - this is my fault, I used the old search_indexes.py file, and my index_queryset() method was wrong. I will not close it, as it may be useful to others.