HTTP output causes Logstash to consume all CPU on DNS resolution failure

[mbrancato]

I've noticed on multiple occasions, that when the HTTP output is configured, but say the hostname is set incorrectly or the network is even down, that Logstash will use all CPU due to a name resolution failure.

• Version: 6.2.4-6.3.0
• Operating System: Linux
• Config File:

output {
  http {
    url => 'https://web.service.net/events'
    http_method => 'post'
    format => 'json_batch'
    headers => ['Authorization', 'XXXXXXXXX']
  }
}

• Steps to Reproduce: configure hostname incorrectly, unplug network, or block DNS