Project: Flink (App Definition and Development / Streaming & Messaging)
File: gcs.md

title: Google Cloud Storage weight: 3 type: docs aliases: /deployment/filesystems/gcs.html <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> (GCS) provides cloud storage for a variety of use cases. You can use it for reading and writing data, and for checkpoint storage when using ) with the . You can use GCS objects like regular files by specifying paths in the following format: ```plain gs://<your-bucket>/<endpoint> ``` The endpoint can either be a single file or a directory, for example: ```java // Read from GCS bucket env.readTextFile("gs://<bucket>/<endpoint>"); // Write to GCS bucket stream.writeAsText("gs://<bucket>/<endpoint>"); // Use GCS as checkpoint storage Configuration config = new Configuration(); config.set(CheckpointingOptions.CHECKPOINT_STORAGE, "filesystem"); config.set(CheckpointingOptions.CHECKPOINTS_DIRECTORY, "gs://<bucket>/<endpoint>"); env.configure(config); ``` Note that these examples are not exhaustive and you can use GCS in other places as well, including your or the ; everywhere that Flink expects a FileSystem URI. Flink provides the `flink-gs-fs-hadoop` file system to write to GCS. This implementation is self-contained with no dependency footprint, so there is no need to add Hadoop to the classpath to use it. `flink-gs-fs-hadoop` registers a `FileSystem` wrapper for URIs with the gs:// scheme. It uses Google's Hadoop library to access GCS. It also uses Google's library to provide `RecoverableWriter` support. This file system can be used with the . To use `flink-gs-fs-hadoop`, copy the JAR file from the `opt` directory to the `plugins` directory of your Flink distribution before starting Flink, i.e. ```bash mkdir ./plugins/gs-fs-hadoop cp ./opt/flink-gs-fs-hadoop-{{< version >}}.jar ./plugins/gs-fs-hadoop/ ``` The underlying Hadoop file system can be configured using the for `gcs-connector` by adding the configurations to your . For example, `gcs-connector` has a `fs.gs.http.connect-timeout` configuration key. If you want to change it, you need to set `gs.http.connect-timeout: xyz` in . Flink will internally translate this back to `fs.gs.http.connect-timeout`. You can also set `gcs-connector` options directly in the Hadoop `core-site.xml` configuration file, so long as the Hadoop configuration directory is made known to Flink via the `env.hadoop.conf.dir` Flink option or via the `HADOOPCONFDIR` environment variable. `flink-gs-fs-hadoop` can also be configured by setting the following options in : | Key | Description | ||-| | gs.writer.temporary.bucket.name | Set this property to choose a bucket to hold temporary blobs for in-progress writes via `RecoverableWriter`. If this property is not set, temporary blobs will be written to same bucket as the final file being written. In either case, temporary blobs are written with the prefix

<br><br> It is recommended to choose a separate bucket in order to , to provide a mechanism to clean up orphaned blobs that can occur when restoring from check/savepoints.<br><br>If you do use a separate bucket with a TTL for temporary blobs, attempts to restart jobs from check/savepoints after the TTL interval expires may fail. | | gs.writer.chunk.size | Set this property to for writes via `RecoverableWriter`. <br><br>If not set, a Google-determined default chunk size will be used. | | gs.filesink.entropy.enabled | Set this property to improve performance due to hotspotting issues on GCS. This option defines whether to enable entropy injection in filesink gcs path. If this is enabled, entropy in the form of temporary object id will be injected in beginning of the gcs path of the temporary objects. The final object path remains unchanged. | | gs.http.connect-timeout | Set this property to for java-storage client. GCS default will be used if not configured. | | gs.http.read-timeout | Set this property to from connection established via java-storage client. GCS default will be used if not configured. | | gs.retry.max-attempt | Set this property to to perform. GCS default will be used if not configured. | | gs.retry.init-rpc-timeout | Set this property to for the initial RPC. Subsequent calls will use this value adjusted according to the gs.retry.rpc-timeout-multiplier. GCS default will be used if not configured. | | gs.retry.rpc-timeout-multiplier | Set this property to . The timeout of the previous call is multiplied by the RpcTimeoutMultiplier to calculate the timeout for the next call. GCS default will be used if not configured. | | gs.retry.max-rpc-timeout | Set this property to on the value of the RPC timeout, so that the max rpc timeout can't increase the RPC timeout higher than this amount. GCS default will be used if not configured. | | gs.retry.total-timeout | Set this property to during which retries could be attempted. GCS default will be used if not configured. | Most operations on GCS require authentication. To provide authentication credentials, either: Set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable to the path of the JSON credentials file, as described , where JobManagers and TaskManagers run. This is the recommended* method. Set the `google.cloud.auth.service.account.json.keyfile` property in `core-site.xml` to the path to the JSON credentials file (and make sure that the Hadoop configuration directory is specified to Flink as described ): ``` <configuration> <property> <name>google.cloud.auth.service.account.json.keyfile</name> <value>PATH TO GOOGLE AUTHENTICATION JSON FILE</value> </property> </configuration> ``` For `flink-gs-fs-hadoop` to use credentials via either of these two methods, the use of service accounts for authentication must be enabled. This is enabled by default; however, it can be disabled in `core-site.xml` by setting: ``` <configuration> <property> <name>google.cloud.auth.service.account.enable</name> <value>false</value> </property> </configuration> ``` {{< hint warning >}} `gcs-connector` supports additional options to provide authentication credentials besides the `google.cloud.auth.service.account.json.keyfile` option described above. However, if you use any of those other options, the provided credentials will not be used by the `google-cloud-storage` library, which provides `RecoverableWriter` support, so Flink recoverable-write operations would be expected to fail. For this reason, use of the `gcs-connector` authentication-credentials options other than `google.cloud.auth.service.account.json.keyfile` is not recommended. {{< /hint >}} {{< top >}}