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

"each host can be either IP, HOST," statement not correct for hosts array scenario #64

Open
ppf2 opened this issue May 2, 2017 · 2 comments
Labels

Comments

@ppf2
Copy link
Member

ppf2 commented May 2, 2017

Documentation on hosts setting for the input is not clear:

https://www.elastic.co/guide/en/logstash/current/plugins-inputs-elasticsearch.html#plugins-inputs-elasticsearch-hosts

It says

List of elasticsearch hosts to use for querying. each host can be either IP, HOST, IP:port or HOST:port port defaults to 9200

But if you have multiple hosts specified as an array, it doesn't know what to default the port to.

So you end up with something like the following for the case of ssl=>true.

[2017-05-01T18:12:36,315][ERROR][logstash.agent           ] Pipeline aborted due to error {:exception=>#<URI::InvalidURIError: the scheme https does not accept registry part: 127.0.0.1:https (or bad hostname?)>,

In others, the statement "each host can be either IP, HOST," is not true if multiple hosts are specified in an array.

@ppf2 ppf2 added the docs label May 2, 2017
@jordansissel
Copy link
Contributor

jordansissel commented May 2, 2017 via email

@ppf2 ppf2 added bug and removed docs labels May 2, 2017
@ppf2
Copy link
Member Author

ppf2 commented May 2, 2017

Removing docs tag and marking it as a bug. This is reproducible on 5.3.0 and the latest logstash-input-elasticsearch (4.0.3). Workaround is to explicitly include the :port in the hosts array specification.

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

No branches or pull requests

2 participants