[NIFI-8048] PutElasticsearchRecord should retry with 503 response

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.12.1
• Fix Version/s: 1.13.0
• Component/s: Extensions
• Assignee: Koji Kawamura
• Reporter: Koji Kawamura
• Created: 26/Nov/20 07:14
• Updated: 26/Nov/20 09:50
• Resolved: 26/Nov/20 09:50

Description

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.

Issue Links

• links to: GitHub Pull Request #4690