-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Unhelpful error message initializing OpenSearch Ingestion & sink #4717
Comments
FOLLOW-UP: looks like there was something wrong with my index mapping. I abbreviated it above, but here's the original:
The problem here was:
But that's pretty much impossible to determine from the logs. |
@elliott-king , Did your pipeline work after you corrected your index mapping? Or does this still occur? |
One of my coworkers encountered an issue like this last week. Our logs have a whole lot of the same "Failure opening selector" exception, but these exceptions were directly preceded by authorization exceptions that he was trying to address.
Here's the IO exception for reference:
He deployed a change to attempt to solve the authorization issue, but I don't know if it had any effect. Anyway, we're still seeing the same IOException. BTW these two particular logs that I posted are adjacent. |
It did work. The source was user error (me), but the logs were still indecipherable. Since my issue was related to the logging output, I left this open. |
This should be fixed by #4758 |
Describe the bug
My pipeline sink/ingestion is failing to initialize, with the following cloudwatch error logs:
There is a similar issue (#4195), but that is an auth issue. Seems like "Failure opening selector" can be a file io issue, but idk how to dive into that.
To Reproduce
I'm basically following the AWS Amplify Opensearch guide, but have an "Events" model instead of "Todos":
Expected behavior
I'd expect the pipeline to work, or more involved logging.
The text was updated successfully, but these errors were encountered: