Conversation
There was a problem hiding this comment.
I faced the same issue for CT env and while testing on our lab, this is how I resolved it. Not sure why in your case we need to go through this path:
My fix:
1. Elasticsearch Index Mapping Conflict
Symptom:
400 - {"error":{"type":"illegal_argument_exception",
"reason":"Mapper for [email_unvalidated] conflicts with existing mapping"}}
Root Cause:
The existing Elasticsearch index had email_unvalidated mapped with a different index setting than what the new Wire version expects. Elasticsearch does not allow changing field mapping properties on an existing index.
Resolution:
Delete the conflicting index and recreate it via the elasticsearch-index subchart:
# Delete the conflicting index
d kubectl exec -n default deployment/brig -- \
curl -X DELETE http://elasticsearch-external:9200/directory
# Run the elasticsearch-index chart standalone
d helm upgrade --install elasticsearch-index \
charts/wire-server/charts/elasticsearch-index \
--set elasticsearch.host=elasticsearch-external \
--set cassandra.host=cassandra-external \
-n default"
| Charts for `elasticsearch-migrate` will be needed: | ||
|
|
||
| ``` | ||
| wget wget https://s3-eu-west-1.amazonaws.com/public.wire.com/charts-develop/elasticsearch-migrate-0.1.0.tgz |
There was a problem hiding this comment.
Why this specific image? What about the chart image?
|
|
||
| ``` | ||
| reindexType: "reindex" | ||
| runReindex: true |
There was a problem hiding this comment.
I could not find any references of both reindexType and runReindex
| index: directory_new | ||
| elasticsearch-index: | ||
| elasticsearch: | ||
| index: directory_new |
There was a problem hiding this comment.
Also did not find any reference of this value directory_new
2 participants
Change type
Basic information
Testing
Tracking