[
https://issues.apache.org/jira/browse/FLINK-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9450:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Job hangs if S3 access it denied during checkpoints
> ---------------------------------------------------
>
> Key: FLINK-9450
> URL: https://issues.apache.org/jira/browse/FLINK-9450
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.4.2
> Reporter: Elias Levy
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> We have a streaming job that consumes from and writes to Kafka. The job is
> configured to checkpoint to S3. If we deny access to S3 by using iptables on
> the TM host to deny all outgoing connections to ports 80 and 443, whether
> using DROP or REJECT, and whether using REJECT with -reject-with tcp-reset or
> -r reject-with imp-port-unreachable, the job soon stops publishing to Kafka.
> This happens whether or not the Kafka sources have
> {{setCommitOffsetsOnCheckpoints}} set to true or false.
> The system is configured to use Presto for the S3 file system. The job has a
> small amount of state, so it is configured to use {{FsStateBackend}} with
> asynchronous snapshots.
> If the ip tables rules are removed, the job continues the function.
> I would expect the job to either fail or continue running if a checkpoint
> fails.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
