Migration Assistant: Add troubleshooting section and resolution for Elasticsearch/Elastic Cloud use with Migration Assistant capture proxy and replayer #11396
Conversation
…Cloud use with Migration Assistant capture proxy and replayer Signed-off-by: Andre Kurait <[email protected]>
AndreKurait
requested review from
AMoo-Miki,
dlvenable,
epugh,
kolchfa-aws,
natebower and
sumobrian
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Signed-off-by: Andre Kurait <[email protected]>
AndreKurait
force-pushed
the
DocumentationForMAWithElasticCloud
branch
from
20630a5 to
776d79f
Compare
Signed-off-by: Andre Kurait <[email protected]>
|
|
||
| ## Troubleshooting | ||
|
|
||
| The following sections may be helpful in diagnosing common issues that arise. If you encounter an issue not documented, incorporate that feedback into this section for future readers. |
There was a problem hiding this comment.
I don't understand what the sentence "If you encounter an issue not documented, incorporate that feedback into this section for future readers." who is 'you' and how does a reader know how to incorporate feedback.
|
|
||
| When migrating to OpenSearch or another service that does not support these Elasticsearch-specific media types, requests from these clients may fail or be rejected by the target cluster. | ||
|
|
||
| **Important**: If you are using Elasticsearch clients with version 7.11 or later and migrating to OpenSearch or a service that does not recognize `application/vnd.elasticsearch+json` media types, you need to apply a transformation to convert both the `Content-Type` and `Accept` headers to the standard `application/json` format. |
There was a problem hiding this comment.
It is also worth noting that the clients will need to be updated so that they behave correctly
| ``` | ||
| {% include copy.html %} | ||
|
|
||
| Next, create a transformation configuration file at `/shared-logs-output/replayer-transformation.json`: |
There was a problem hiding this comment.
Future: It's nice to have these here for illustrative purposes, but why are we adding these transforms to documentation an not the repo/distro?
| ### Host header routing configuration | ||
|
|
||
| You can check the indexes and document counts of the source and target clusters by running the `cat-indices` command. This can be used to monitor the difference between the source and target for any migration scenario. Check the indexes of both clusters using the following command: | ||
| Some systems, such as Elastic Cloud and other hosted Elasticsearch services, use the Host header for routing traffic to the appropriate cluster. When using the Capture Proxy with these systems, you need to configure the proxy to set the Host header to match your source cluster's domain. |
There was a problem hiding this comment.
I would add to the end of this sentence something like "your source cluster's domain since clients may be setting the host otherwise to the proxy". Make it clear that this isn't a proxy bug but a more general client/configuration issue.
| {% include copy.html %} | ||
|
|
||
| You should receive the following response: | ||
| For example, if your Elastic Cloud domain is `https://my-cluster.es.us-east-1.aws.found.io`, you would configure: |
There was a problem hiding this comment.
not sure what found.io is (found.no was acquired by Elastic) - can you use example.com as a TLD?
4 participants
Description
Add troubleshooting section and resolution for Elasticsearch/Elastic Cloud use with Migration Assistant capture proxy and replayer
Issues Resolved
N/A
Version
Migration Assistant 2.x+
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.