[ https://issues.apache.org/jira/browse/NIFI-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498066#comment-16498066 ]
John Smith commented on NIFI-4410: ---------------------------------- We're still seeing this problem in NiFi 1.6.0. We're using Elasticsearch 6.2.4 > PutElasticsearchHttp needs better error handling and logging > ------------------------------------------------------------ > > Key: NIFI-4410 > URL: https://issues.apache.org/jira/browse/NIFI-4410 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Reporter: Joseph Witt > Assignee: Matt Burgess > Priority: Major > Fix For: 1.6.0 > > > https://github.com/apache/nifi/blob/6b5015e39b4233cf230151fb45bebcb21df03730/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L364-L366 > If it cannot extract the reason text it provides a very generic error and > there is nothing else logged. You get no context as to what went wrong and > further the condition doesn't cause yielding or anything so there is just a > massive flood of errors in logs that dont' advise the user of the problem. > We need to make sure the information can be made available to help > troubleshoot and we need to cause yielding so that such cases do not cause > continuous floods of errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005)