Skip to content
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

cxn_pool can't be Static #1

Open
pjlsergeant opened this issue Jul 27, 2018 · 2 comments
Open

cxn_pool can't be Static #1

pjlsergeant opened this issue Jul 27, 2018 · 2 comments

Comments

@pjlsergeant
Copy link

If cxn_pool is set to Static -- which is the default -- then this gives a rather cryptic 401 and says no nodes can be found. This was deeply confusing. It would be worth noting in the docs that cxn_pool => 'Static::NoPing' will stop the initial HEAD method from being nuked.

@pplu
Copy link
Owner

pplu commented Jul 27, 2018

We're running with cxn_pool set to Static without problems.

What version of ElasticSearch are you running? Is it a multinode cluster?

@pjlsergeant
Copy link
Author

My bad here. Combined with #2 the actual problem here is just that AWS gives an exceptionally opaque error message if credentials fail, and the module here doesn't (all that surprisingly) pick up on that.

I guess you can reproduce by seeing the difference in the error message you get -- with incorrect credentials -- when cxn_pool is Static vs Static::NoPing. For me the former simply reports the node as dead, the latter gives an actual "Your signature is wrong etc" msg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants