[
https://issues.apache.org/jira/browse/FLINK-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-13597.
------------------------------------
Resolution: Fixed
I did some testing on a Google Cloud Dataproc cluster (it gives you a managed
YARN and Google Cloud Storage (GCS)):
- tried both YARN session mode and YARN per-job mode, also using bin/flink
list/cancel/etc. against a YARN session cluster
- ran examples that write to GCS, both with the native Hadoop FileSystem and a
custom “plugin” FileSystem
- ran stateful streaming jobs that use GCS as a checkpoint backend
- tried running SQL programs on YARN using the SQL Cli: this worked for YARN
session mode but not for YARN per-job mode. Looking at the code I don’t think
per-job mode would work from seeing how it is implemented. But I think it’s an
OK restriction to have for now
- in all the testing I had fine-grained recovery (region failover) enabled but
I didn’t simulate any failures
> Test Flink 1.9.0 on cluster
> ---------------------------
>
> Key: FLINK-13597
> URL: https://issues.apache.org/jira/browse/FLINK-13597
> Project: Flink
> Issue Type: Test
> Components: Tests
> Affects Versions: 1.9.0
> Reporter: Till Rohrmann
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: 1.9.0
>
>
> In order to verify the Flink {{1.9.0}} release, we should try it out on one
> of the available cloud providers (AWS, GCP). I would suggest to run a
> non-trivial workload on the cluster with using some of the new features:
> - SQL job
> - Filesystem being loaded as a plugin
> - Enable fine-grained recovery for batch job
> - Java 9
> - Checkpoints to GFS
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
