Skip to content

c2c: physical cluster replication effectively hangs on ~10 GB import #105676

Closed
Closed
c2c: physical cluster replication effectively hangs on ~10 GB import#105676
Assignees
stevendanna
Labels
A-disaster-recoveryC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-test-failureBroken test (automatically or manually discovered).T-disaster-recoverydb-cy-23
@msbutler

Description

@msbutler
msbutler
opened on Jun 28, 2023

In the reduced version of the c2c/BulkOps roachtest(#105677), a 10GB import runs on the source cluster after the replication stream begins. The import takes about 3 minutes, yet after an hour, the replication stream's hwm fails to advance past the import's completion time. At first, the destination side addSStable application rate seems fine, but then slows to a crawl. We should figure out why this occurs.

Jira issue: CRDB-29147

Metadata

Metadata

Assignees

Labels

A-disaster-recoveryC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-test-failureBroken test (automatically or manually discovered).T-disaster-recoverydb-cy-23

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions