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

RavenDB-22279 - ClusterWideTransaction_WhenRestoreFromIncrementalBackupAfterStoreAndDelete_ShouldDeleteInTheDestination fails on sharding #18462

Merged
merged 3 commits into from May 6, 2024

Conversation

shaharhikri
Copy link
Contributor

@shaharhikri shaharhikri commented May 1, 2024

Issue link

https://issues.hibernatingrhinos.com/issue/RavenDB-22279/SlowTests.Issues.RavenDB21050.ClusterWideTransactionWhenRestoreFromIncrementalBackupAfterStoreAndDeleteShouldDeleteInTheDestinat

Additional description

SaveChanges for ClusterWideTransaction on sharded db is waiting for index notification only on the ClusterStateMachine and not on the shards, so the backup is ending before the shareds perform the cluster-wide transactions commands.
On restore, we don't need to wait because the cluster transactions are executed directly on the shards DocumentDatabase for each backup file.

Type of change

  • Bug fix
  • Regression bug fix
  • Optimization
  • New feature

How risky is the change?

  • Low
  • Moderate
  • High
  • Not relevant

Backward compatibility

  • Non breaking change
  • Ensured. Please explain how has it been implemented?
  • Breaking change
  • Not relevant

Is it platform specific issue?

  • Yes. Please list the affected platforms.
  • No

Documentation update

  • This change requires a documentation update. Please mark the issue on YouTrack using Documentation Required tag.
  • No documentation update is needed

Testing by Contributor

  • Tests have been added that prove the fix is effective or that the feature works
  • Internal classes added to the test class (e.g. entity or index definition classes) have the lowest possible access modifier (preferable private)
  • It has been verified by manual testing

Testing by RavenDB QA team

  • This change requires a special QA testing due to possible performance or resources usage implications (CPU, memory, IO). Please mark the issue on YouTrack using QA Required tag.
  • No special testing by RavenDB QA team is needed

Is there any existing behavior change of other features due to this change?

  • Yes. Please list the affected features/subsystems and provide appropriate explanation
  • No

UI work

  • It requires further work in the Studio. Please mark the issue on YouTrack using Studio Required tag.
  • No UI work is needed

@github-actions github-actions bot added the v6.0 label May 1, 2024
Copy link
Contributor

@karmeli87 karmeli87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check failing tests

…upAfterStoreAndDelete_ShouldDeleteInTheDestination fails on sharding
}


[RavenTheory(RavenTestCategory.BackupExportImport)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sharding as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@arekpalinski arekpalinski merged commit 9327ff8 into ravendb:v6.0 May 6, 2024
14 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants