DOC-287 Mountable TS topics #725
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| . Enable xref:manage:tiered-storage.adoc[Tiered Storage] for specific topics, or for the entire cluster (all topics). | ||
| . xref:get-started:rpk-install.adoc[Install `rpk`], or ensure that you have access to the Admin API. | ||
|
|
There was a problem hiding this comment.
Are there any limitations that users should know about? For example, number of topics you can include in a migration? Amount of time that a topic can "hibernate" in object storage until it is mounted (although maybe that's more to do with their object storage configuration)?
There was a problem hiding this comment.
I'm not aware of any limitations like this. I've successfully ran it with as many topics and partitions as I had no problems to create.
There was a problem hiding this comment.
@bashtanov I saw in the rpk PR that a topic must have at least 3 partitions for it to be mounted from TS to a cluster, does that apply anywhere in this doc as well?
There was a problem hiding this comment.
I never enforced or even heard about this restriction
There was a problem hiding this comment.
I saw that in the RFC for migrations, no idea if it is actually true as the testing at the time I wrote that was against a version of migrations that wasn't actually working.
kbatuigas
changed the title
kbatuigas
force-pushed
the
2504_mountable-ts
branch
from
ad98b60
to
99d3851
Compare
|
|
||
| | `executing` | ||
| | The cluster rejects client reads and writes for the topics. Redpanda uploads any remaining topic data that has not yet been copied to object storage. | ||
| | The target cluster starts topic partitions with log segments downloaded from object storage. |
There was a problem hiding this comment.
not yet, the cluster just checks the topic data in tiered storage is not mounted by this or any other cluster
There was a problem hiding this comment.
not yet, the cluster just checks the topic data in tiered storage is not mounted by this or any other cluster
Can | The target cluster starts topic partitions with log segments downloaded from object storage. be moved to the next row executed? If not I'll delete entirely
There was a problem hiding this comment.
Topic partitions are started in preparing state, but clients are not given access to it. Subsequent stages for a mount are only about mount manifest manipulation and eventually lifting these restrictions. I'm not sure whether log segments are physically downloaded on topic creation or when it is read from/written into, maybe storage team knows.
Co-authored-by: Angela Simms <[email protected]>
Co-authored-by: Joyce Fee <[email protected]>
Deflaimun
force-pushed
the
2504_mountable-ts
branch
from
5c91c38
to
947a1da
Compare
Description
Resolves https://github.com/redpanda-data/documentation-private/issues/2504
Related: Migrations API reference
Review deadline: 9 Oct.
Page previews
24.3 beta: Mountable Topics
Checks