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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239155#comment-17239155 ] 

ASF subversion and git services commented on NIFI-8048:
-------------------------------------------------------

Commit 5ea18f39b572b9c552ed066f32be08f14384452d in nifi's branch refs/heads/main from Koji Kawamura
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5ea18f3 ]

NIFI-8048 PutElasticsearchRecord should retry with 503 response

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #4690.


> 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
>          Time Spent: 10m
>  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)