Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce 24-1-async-replication #5418

Conversation

CyberROFL
Copy link
Member

Changelog entry

Asynchronous replication between ydb databases.

Changelog category

  • New feature

Additional information

...

@CyberROFL CyberROFL requested a review from a team as a code owner June 10, 2024 16:16
@CyberROFL CyberROFL changed the base branch from stable-24-1 to stable-24-1-async-replication June 10, 2024 16:17
Copy link

github-actions bot commented Jun 10, 2024

2024-06-10 16:24:20 UTC Pre-commit check for 08a73a0 has started.
2024-06-10 16:24:22 UTC Build linux-x86_64-relwithdebinfo is running...
🟢 2024-06-10 17:15:38 UTC Build successful.
2024-06-10 17:15:54 UTC Tests are running...
🔴 2024-06-10 18:57:21 UTC Some tests failed, follow the links below.

Test history

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
60464 51035 0 2 9342 85

Copy link

github-actions bot commented Jun 10, 2024

2024-06-10 16:31:28 UTC Pre-commit check for 08a73a0 has started.
2024-06-10 16:31:31 UTC Build linux-x86_64-release-asan is running...
🟢 2024-06-10 17:27:40 UTC Build successful.
2024-06-10 17:27:52 UTC Tests are running...
🔴 2024-06-10 19:17:33 UTC Some tests failed, follow the links below.

Test history

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
16140 16042 0 14 58 26

@CyberROFL CyberROFL merged commit 4002b4c into ydb-platform:stable-24-1-async-replication Jun 10, 2024
2 of 4 checks passed
@CyberROFL CyberROFL deleted the 24-1-async-replication branch June 10, 2024 19:25
@CyberROFL CyberROFL mentioned this pull request Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants