Use AWS S3 offloader with Pulsar

Follow the steps below to install the AWS S3 offloader.

  • Pulsar: 2.4.2 or later versions

This example uses Pulsar 2.5.1.

  1. Download the Pulsar tarball using one of the following ways:

  1. Download and untar the Pulsar offloaders package.

    2. wget https://downloads.apache.org/pulsar/pulsar-2.5.1/apache-pulsar-offloaders-2.5.1-bin.tar.gz
    3. tar xvfz apache-pulsar-offloaders-2.5.1-bin.tar.gz

  1. Copy the Pulsar offloaders as offloaders in the Pulsar directory.

    2. mv apache-pulsar-offloaders-2.5.1/offloaders apache-pulsar-2.5.1/offloaders
    4. ls offloaders
  1. **Output**
  3. As shown from the output, Pulsar uses [Apache jclouds](https://jclouds.apache.org) to support [AWS S3](https://aws.amazon.com/s3/) and [GCS](https://cloud.google.com/storage/) for long term storage.
  5. ```
  7. tiered-storage-file-system-2.5.1.nar
  8. tiered-storage-jcloud-2.5.1.nar
  10. ```
  14. ##### note
  16. -   If you are running Pulsar in Docker or deploying Pulsar using a Docker image (such as K8s and DCOS), you can use the `apachepulsar/pulsar-all` image instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
note

Before offloading data from BookKeeper to AWS S3, you need to configure some properties of the AWS S3 offload driver.

Besides, you can also configure the AWS S3 offloader to run it automatically or trigger it manually.

You can configure the AWS S3 offloader driver in the configuration file broker.conf or standalone.conf.

  • Required configurations are as below.

  • Optional configurations are as below.

Bucket (required)

A bucket is a basic container that holds your data. Everything you store in AWS S3 must be contained in a bucket. You can use a bucket to organize your data and control access to your data, but unlike directory and folder, you cannot nest a bucket.

Example
  2. s3ManagedLedgerOffloadBucket=pulsar-topic-offload

Bucket region

A bucket region is a region where a bucket is located. If a bucket region is not specified, the default region (US East (N. Virginia)) is used.

tip

For more information about AWS regions and endpoints, see here.

Example

This example sets the bucket region as europe-west-3.

Authentication (required)

To be able to access AWS S3, you need to authenticate with AWS S3.

Pulsar does not provide any direct methods of configuring authentication for AWS S3, but relies on the mechanisms supported by the .

Once you have created a set of credentials in the AWS IAM console, you can configure credentials using one of the following methods.

  • Use EC2 instance metadata credentials.

    If you are on AWS instance with an instance profile that provides credentials, Pulsar uses these credentials if no other mechanism is provided.

  • Set the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in conf/pulsar_env.sh.

    “export” is important so that the variables are made available in the environment of spawned processes.

    2. export AWS_ACCESS_KEY_ID=ABC123456789
    3. export AWS_SECRET_ACCESS_KEY=ded7db27a4558e2ea8bbf0bf37ae0e8521618f366c

  • Add the Java system properties and aws.secretKey to PULSAR_EXTRA_OPTS in conf/pulsar_env.sh.

    2. PULSAR_EXTRA_OPTS="${PULSAR_EXTRA_OPTS} ${PULSAR_MEM} ${PULSAR_GC} -Daws.accessKeyId=ABC123456789 -Daws.secretKey=ded7db27a4558e2ea8bbf0bf37ae0e8521618f366c -Dio.netty.leakDetectionLevel=disabled -Dio.netty.recycler.maxCapacity.default=1000 -Dio.netty.recycler.linkCapacity=1024"

  • Set the access credentials in ~/.aws/credentials.

    2. [default]
    3. aws_access_key_id=ABC123456789
    4. aws_secret_access_key=ded7db27a4558e2ea8bbf0bf37ae0e8521618f366c

  • Assume an IAM role.

    This example uses the DefaultAWSCredentialsProviderChain for assuming this role.

    2. s3ManagedLedgerOffloadRole=<aws role arn>
    3. s3ManagedLedgerOffloadRoleSessionName=pulsar-s3-offload

Size of block read/write

You can configure the size of a request sent to or read from AWS S3 in the configuration file broker.conf or standalone.conf.

Namespace policy can be configured to offload data automatically once a threshold is reached. The threshold is based on the size of data that a topic has stored on a Pulsar cluster. Once the topic reaches the threshold, an offloading operation is triggered automatically.

Automatic offloading runs when a new segment is added to a topic log. If you set the threshold on a namespace, but few messages are being produced to the topic, offloader does not work until the current segment is full.

You can configure the threshold size using CLI tools, such as pulsar-admin.

The offload configurations in broker.conf and standalone.conf are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command command.

Example

This example sets the AWS S3 offloader threshold size to 10 MB using pulsar-admin.

tip

For more information about the pulsar-admin namespaces set-offload-threshold options command, including flags, descriptions, and default values, see here.

For individual topics, you can trigger AWS S3 offloader manually using one of the following methods:

  • Use REST endpoint.

  • Use CLI tools (such as pulsar-admin).

    To trigger it via CLI tools, you need to specify the maximum amount of data (threshold) that should be retained on a Pulsar cluster for a topic. If the size of the topic data on the Pulsar cluster exceeds this threshold, segments from the topic are moved to AWS S3 until the threshold is no longer exceeded. Older segments are moved first.

Example

  • This example triggers the AWS S3 offloader to run manually using pulsar-admin.

    2. bin/pulsar-admin topics offload --size-threshold 10M my-tenant/my-namespace/topic1
  1. **Output**
  3. ```
  5. Offload triggered for persistent://my-tenant/my-namespace/topic1 for messages before 2:0:-1
  7. ```
  11. ##### tip
  13. For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).

  • This example checks the AWS S3 offloader status using pulsar-admin.

    2. bin/pulsar-admin topics offload-status persistent://my-tenant/my-namespace/topic1
  1. **Output**
  3. ```
  5. Offload is currently running
  6. ```
  10. To wait for the AWS S3 offloader to complete the job, add the `-w` flag.
  12. ```
  14. bin/pulsar-admin topics offload-status -w persistent://my-tenant/my-namespace/topic1
  16. ```
  20. **Output**
  22. ```
  24. Offload was a success
  26. ```
  30. If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
  32. ```
  34. bin/pulsar-admin topics offload-status persistent://my-tenant/my-namespace/topic1
  36. ```
  40. **Output**
  42. ```
  44. Error in offload
  45. null
  47. Reason: Error offloading: org.apache.bookkeeper.mledger.ManagedLedgerException: java.util.concurrent.CompletionException: com.amazonaws.services.s3.model.AmazonS3Exception: Anonymous users cannot initiate multipart uploads.  Please authenticate. (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 798758DE3F1776DF; S3 Extended Request ID: dhBFz/lZm1oiG/oBEepeNlhrtsDlzoOhocuYMpKihQGXe6EG8puRGOkK6UwqzVrMXTWBxxHcS+g=), S3 Extended Request ID: dhBFz/lZm1oiG/oBEepeNlhrtsDlzoOhocuYMpKihQGXe6EG8puRGOkK6UwqzVrMXTWBxxHcS+g=
  49. ```
  53. ##### tip
  54. For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).

For the complete and step-by-step instructions on how to use the AWS S3 offloader with Pulsar, see here.