You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
On Mon, May 1, 2017 at 6:14 PM Pius ***@***.***> wrote:
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.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#64>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIC6hqVxl9_AG37P0wBykl1M_4_3W0Mks5r1oN1gaJpZM4NNm4j>
.
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.
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
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.
In others, the statement "each host can be either IP, HOST," is not true if multiple hosts are specified in an array.
The text was updated successfully, but these errors were encountered: