When events cannot be encoded by the output because they contain invalid values as NaN they should be dropped as the Elasticsearch output does.
But at least with logstash output the observed behaviour is that the whole batch including the wrong event is retried and/or dropped, leading to repeated or missing events, and to repeating messages in logs as the wrong event is also retried.