This has been resolved Logstash team was super quick in resolving this issue elastic/logstash#8379 This issue is fixed since logstash v5.6.3