Closed
Bug 1116149
Opened 10 years ago
Closed 7 years ago
create setup script for elasticsearch
Categories
(Socorro :: General, task, P2)
Socorro
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lars, Assigned: osmose)
References
Details
an external user of Socorro has been having trouble getting going because of elastic search setup troubles.
the docs say to invoke ```scripts/setup_elasticsearch_app.py```, but that does not exist. Instead, there is ```scripts/setup_supersearch_app.py```. However, that app fails if the current working directory is not .../scripts
In the same manner that the setup for Postgres is in .../socorro/external/postgresql, the setup for elastic search should be packaged with the rest of the elastic search code in .../socorro/external/es. Then an alias should be added for the ES setup app to the file .../socorro/app/for_application_defaults.py:50
That will then allow the ES setup app to follow the rest the rest of the apps with an invocation like:
socorro setup_supersearch
Comment 1•7 years ago
|
||
This is something along the lines of what Mike and I were talking about a couple of weeks ago. I'm going to toss it in the queue. It'd help with local development since it would make it possible to manage ES indexes without having to process crashes for the side-effect that saving a processed crash in ES creates an index.
OS: Linux → All
Priority: -- → P2
Hardware: x86_64 → All
Summary: elasticsearch setup fails → create setup script for elasticsearch
Comment 3•7 years ago
|
||
Assigning this to Mike since he built something similarish just now.
Assignee: nobody → mkelly
Assignee | ||
Comment 4•7 years ago
|
||
scripts/setup_supersearch_app.py doesn't exist anymore, and I can't find any other initialization of elasticsearch in the repo. The local development environment uses a standard elasticsearch image. Index creation currently happens when a crash is processed; bug 1430862 will move that to a crontabber job. We're also adding some index cleanup and initialization to the local development lifecycle commands in bug 1399305. I can't find the docs mentioned in the summary either.
Given all that, I don't think there's anything to do here.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•