[
https://issues.apache.org/jira/browse/NIFI-15759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070082#comment-18070082
]
ASF subversion and git services commented on NIFI-15759:
--------------------------------------------------------
Commit 8605e0d4a8d19ddcdcbbee6fa89340c023b9d2d3 in nifi's branch
refs/heads/dependabot/npm_and_yarn/nifi-frontend/src/main/frontend/handlebars-4.7.9
from Alaksiej Ščarbaty
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8605e0d4a8d ]
NIFI-15759 Handle ResourceNotFoundException in ConsumeKinesis (#11060)
> Handle ResourceNotFoundException gracefully in ConsumeKinesis for deleted
> shards
> --------------------------------------------------------------------------------
>
> Key: NIFI-15759
> URL: https://issues.apache.org/jira/browse/NIFI-15759
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 2.8.0
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Major
> Fix For: 2.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When a Kinesis stream is resharded or deleted, accessing shards that no
> longer exist results in ResourceNotFoundException from the AWS SDK.
> Currently, neither the Enhanced Fan-Out (EFO) nor the polling consumer
> handles this exception, resulting in:
> • Repeated ERROR-level log messages until the 60-second shard cache TTL
> expires and the shard is dropped from the active set;
> • In EFO mode, the ShardConsumer continuously resubscribes to the deleted
> shard every 5 seconds;
> • Unnecessary noise in logs for what is expected operational behavior
> during resharding.
> The processor should stop consuming data from a Shard whenever
> ResourceNotFoundException is encounted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
