Clarify support for cross region Tiered Storage / RRR #942
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| You need the following: | ||
|
|
||
| * An origin cluster with xref:{tiered-storage-link}#set-up-tiered-storage[Tiered Storage] set up. | ||
| * An origin cluster with xref:{tiered-storage-link}#set-up-tiered-storage[Tiered Storage] set up. Note that multi-region buckets or containers are not supported. |
There was a problem hiding this comment.
My understanding is that it's specifically the object storage bucket (for the TS setup) that has to be single-region and not multi-region. Would like to double check that this is the best place in this doc to add a heads-up regarding multi-region?
There was a problem hiding this comment.
I'm OK with keeping it this way. RRR will work with both single reagion and multi-region buckets but we only test with single region.
| * A separate remote cluster in the same region as the bucket or container used for the origin cluster. | ||
| ** If you use a multi-region bucket/container, you can create the read replica cluster in any region that has that bucket/container. | ||
| ** If you use a single-region bucket/container, the remote cluster must be in the same region as the bucket/container. | ||
| * A separate remote cluster. This cluster can be in the same or a different region as the bucket or container used for the origin cluster. |
There was a problem hiding this comment.
Our version of RRR doc for Cloud says:
Prerequisites
- A BYOC reader cluster in Ready state. This separate reader cluster must exist in the same Redpanda organization and the same cloud provider account and region as the source cluster.
Does this need to be edited? It seems to me that the prereq regarding the region can be changed, but I'm not sure about it the reader cluster having to be in the same RP org and cloud account still.
There was a problem hiding this comment.
To further complicate things, different region is only supported in GCP right now. Not in AWS. RRR is not at all supported in Azure.
There was a problem hiding this comment.
If it's that deep, maybe we should add a table or something about the 3 different providers.
There was a problem hiding this comment.
Oh, interesting: thanks @frenchfrywpepper! I've added to this other PR about beta/LA features. Please also update that PR with any other info you know about beta/LA features.
I don't think a table for the providers is necessary here. I'd just note the difference for providers in the Prereqs.
Co-authored-by: Paulo Borges <[email protected]>
| . Create a remote cluster for the Remote Read Replica topic. | ||
| * If that's a multi-region bucket/container, you can create the read replica cluster in any region that has that bucket/container. | ||
| * If that's a single-region bucket/container, the remote cluster must be in the same region as the bucket/container. | ||
| . Create a remote cluster for the Remote Read Replica topic. The remote cluster can be in the same or a different region as the bucket/container. |
There was a problem hiding this comment.
Should you have the same info here in the step; i.e., for AWS, the remote cluster must be in the same region as the origin cluster, but for GCP, the remote cluster can be in the same or a different region as the origin cluster.
micheleRP
left a comment
micheleRP
left a comment
There was a problem hiding this comment.
left some comments, but looks good!
| ** If you use a multi-region bucket/container, you can create the read replica cluster in any region that has that bucket/container. | ||
| ** If you use a single-region bucket/container, the remote cluster must be in the same region as the bucket/container. | ||
| * A separate remote cluster. | ||
| ** AWS: The remote cluster must be in the same region as the origin cluster. |
There was a problem hiding this comment.
Just checking - is this a feature of BYOC rather than AWS in general?
There was a problem hiding this comment.
The fact that for AWS the cluster must be in the same region is a limitation of Redpanda Core. https://redpandadata.slack.com/archives/C0191NM4WU9/p1733252862922189
There was a problem hiding this comment.
Confirming whether this should specifically mention the origin cluster's storage bucket. Does Tiered Storage require that the bucket be in the same region as the cluster? I think it's implied but our docs don't explicitly state that.
| ** If you use a multi-region bucket/container, you can create the read replica cluster in any region that has that bucket/container. | ||
| ** If you use a single-region bucket/container, the remote cluster must be in the same region as the bucket/container. | ||
| * A separate remote cluster. | ||
| ** AWS: The remote cluster must be in the same region as the origin cluster's storage bucket/container. |
There was a problem hiding this comment.
So sorry, these 3 bits of information are applicable to Cloud. I can't speak to the self-managed side. Sorry I wasn't paying attention and steered you wrong. :(
kbatuigas
deleted the
DOC-809-Tiered-storage-recommendations-for-region-vs-multi-region-buckets
branch
Description
Based on this discussion, we should
TODO
Resolves https://github.com/redpanda-data/documentation-private/issues/
Review deadline: 10 Jan
Page previews
Remote Read Replicas
Tiered Storage > Limitations
Checks