...but when I looked at the running containers, I saw that Elasticsearch was unhealthy:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a5b28f4215df may-release-2-frontend "nginx -g 'daemon of…" 18 minutes ago Up 18 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:32793->80/tcp, 0.0.0.0:32792->443/tcp may-release-2_frontend_1
693b7b546d4a may-release-2 "bash -c 'uwsgi /opt…" 18 minutes ago Up 18 minutes 0.0.0.0:32791->5000/tcp may-release-2_web-api_1
a653dfb28fca may-release-2 "bash -c 'celery wor…" 18 minutes ago Up 18 minutes may-release-2_worker_1
34cd7e0ce491 may-release-2 "bash -c 'uwsgi /opt…" 18 minutes ago Up 18 minutes 0.0.0.0:32790->5000/tcp may-release-2_web-ui_1
e70d2f703327 rabbitmq:3-management "docker-entrypoint.s…" 18 minutes ago Up 18 minutes 4369/tcp, 5671/tcp, 0.0.0.0:5672->5672/tcp, 15671/tcp, 25672/tcp, 0.0.0.0:15672->15672/tcp may-release-2_mq_1
0c3b9d446c9d postgres:9.6 "docker-entrypoint.s…" 18 minutes ago Up 18 minutes 0.0.0.0:5432->5432/tcp may-release-2_db_1
37ef25a56179 redis "docker-entrypoint.s…" 18 minutes ago Up 18 minutes 0.0.0.0:6379->6379/tcp may-release-2_cache_1
a5fdaa00ca62 docker.elastic.co/elasticsearch/elasticsearch-oss:7.2.0 "/usr/local/bin/dock…" 18 minutes ago Up 18 minutes (unhealthy) 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp may-release-2_es_1
I loaded https://127.0.0.1/ in the browser and was able to successfully search the demo data:
I ran several other searches of the demo data and didn't notice any errors or unexpected behavior. I then created my own record:
When I tried to search for this, I got an error:
There seemed to be a search indexing problem with Elasticsearch, because while I couldn't find the record with the text "Datalab" (shown above) or with my last name:
...I was able to find it with my first name:
As a side note, I ran through the install process a couple of times and while the search errors were similar in both cases, the specific search terms that worked vs. the ones that generated an error differed between the two tries.
I've installed the May release using the following procedure:
Everything seems to have been installed correctly and completed successfully...
...but when I looked at the running containers, I saw that Elasticsearch was unhealthy:
I loaded
https://127.0.0.1/
in the browser and was able to successfully search the demo data:I ran several other searches of the demo data and didn't notice any errors or unexpected behavior. I then created my own record:
When I tried to search for this, I got an error:
There seemed to be a search indexing problem with Elasticsearch, because while I couldn't find the record with the text "Datalab" (shown above) or with my last name:
...I was able to find it with my first name:
As a side note, I ran through the install process a couple of times and while the search errors were similar in both cases, the specific search terms that worked vs. the ones that generated an error differed between the two tries.