[jira] [Resolved] (NIFI-8048) PutElasticsearchRecord should retry with 503 response

["Pierre Villard (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-8048.
----------------------------------
    Fix Version/s: 1.13.0
       Resolution: Fixed

> PutElasticsearchRecord should retry with 503 response
> -----------------------------------------------------
>
>                 Key: NIFI-8048
>                 URL: https://issues.apache.org/jira/browse/NIFI-8048
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.12.1
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>            Priority: Minor
>             Fix For: 1.13.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During Elasticsearch full cluster restart, PutElasticseachRecord routed incoming FlowFiles to its 'failure' relationship. In contrast, PutElasticsearchHttp / PutElasticsearchHttpRecord routed incoming FlowFiles to 'retry'.
> While PutElasticsearchHttp processors determine if a request can be retried by checking if HTTP status code is 5XX, PutElasticsearchRecord and corresponding ElasticsearchError only check the name of thrown exception.
> To make PutElasticsearchRecord more resilient against such situation, ElasticsearchError should treat ResponseException as recoverable where HTTP status code is 503 Service Unavailable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)