summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Allow to cancel waiting tasks for non-existing repos without scheduling themv3.3.11upstream/stable-3.3Saša Živkov2022-05-023-4/+43
| | | | | | | | | | | | | | | | | | A waiting task for a non-existing repository can come into existence when the repository gets deleted before a waiting task gets scheduled, and thus becomes a running task. A waiting task for a non-existing repository cannot be (re)scheduled because there is a check for repository existence in that code-path. However, such a task would remain in the waiting queue and rescheduling would be tried again and again without a chance to get finished as the only way for a task to get finished was to run it. This change allows to finish a waiting task when its repository doesn't exist. The ReplicationTasksStorage now tries to delete task file(s) from both running and waiting directories. Change-Id: Ibbdd5023e2a008484215da02403c9935d21fbf13
* Do not retry replication when local repository not foundSaša Živkov2022-04-012-1/+18
| | | | | | | | | | | | | | | | | | | When many repositories get created and deleted in a quick succession it may happen that a repository gets deleted before its replication task starts. Such replication task will keep retrying, possibly indefinitely, but has no chance to succeed. Another scenario where this issue can occur is when a repository gets created but a replica is not reachable for some time. If the repository gets deleted before the replica gets reachable again, the replication task will keep retrying but the local repository will not exist. When handling the RepositoryNotFoundException in PushOne, set the retrying flag to false. This ensures that this replication task is not retried and gets finished. Bug: Issue 15804 Change-Id: Ia55c5ec1c961f4c2aec9ecee8056f22b436e9fda
* Merge branch 'stable-3.2' into stable-3.3v3.3.9v3.3.10Luca Milanesio2021-11-261-1/+10
|\ | | | | | | | | | | | | | | * stable-3.2: Doc: make explicit that remoteNameStyle is for non-Gerrit repos Doc: remoteNameStyle might result in a repo name clashes Change-Id: I32d598a36fe20c469528eca8d4c10d8775f7a3c4
| * Merge "Doc: remoteNameStyle might result in a repo name clashes" into stable-3.2upstream/stable-3.2Jacek Centkowski2021-11-261-0/+8
| |\
| | * Doc: remoteNameStyle might result in a repo name clashesLuca Milanesio2021-11-251-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When using the remoteNameStyle in the replication.config settings the Gerrit admin needs to be warned on the risks of using sytles that may be ambiguous and associate two source repositories to the same target repository on the replica. Example: set remoteNameStyle to basenameOnly /foo/my-repo.git => pushed to my-repo /bar/my-repo.git => pushed to my-repo When two commits are pushed to the same branch on the two repos /foo/my-repo.git and /bar/my-repo.git, the replication plugin would push them to the same target repo my-repo, causing clashes and losing commits (depending which one is pushed first). The risk needs to be highlighted so that the Gerrit admin can check that univocity of the mapping is respected. Bug: Issue 15315 Change-Id: Iba42907bceb8d1c27d739f3b0cded4a1d7400686
| * | Doc: make explicit that remoteNameStyle is for non-Gerrit reposLuca Milanesio2021-11-251-1/+2
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The documentation already specify non-Gerrit examples of use of remoteNameStyle; however, it does not say that if the remote repository is backed by Gerrit, the *ONLY* supported option is "slashes", otherwise the consequences could be catastrophic. Two Gerrit servers (e.g. primary and replica) need to have full alignment of repository names, as they are also referenced in the inherited ACLs. Having a repository name mapping, may disrupt the ACLs evaluation and make the remote Gerrit replica unusable. Bug: Issue 15318 Change-Id: I4d9447a4d0366a98037470c0cceda36f7a1b8a25
* | Merge branch 'stable-3.2' into stable-3.3v3.3.8v3.3.7v3.3.6v3.3.5v3.3.4v3.3.3Nasser Grainawi2021-02-252-22/+23
|\| | | | | | | | | | | | | | | * stable-3.2: Call retryDone() when giving up after lock failures Fix issue with task cleanup after retry Change-Id: I03b5bbfcfca75a3ee54e782e4b64f19b1100e2eb
| * Merge branch 'stable-3.1' into stable-3.2v3.2.9v3.2.8v3.2.14v3.2.13v3.2.12v3.2.11v3.2.10Nasser Grainawi2021-02-252-22/+23
| |\ | | | | | | | | | | | | | | | | | | | | | * stable-3.1: Call retryDone() when giving up after lock failures Fix issue with task cleanup after retry Change-Id: I6dbeaa0d21545a1903bdb11c5de5d9e8f72079c5
| | * Merge branch 'stable-3.0' into stable-3.1v3.1.16v3.1.15v3.1.14v3.1.13upstream/stable-3.1Nasser Grainawi2021-02-252-16/+18
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.0: Call retryDone() when giving up after lock failures Fix issue with task cleanup after retry Change-Id: Id9ce63cd6112b3c8b16f9daafe3a8a982521baa9
| | | * Merge branch 'stable-2.16' into stable-3.0upstream/stable-3.0Nasser Grainawi2021-02-254-14/+39
| | | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-2.16: Call retryDone() when giving up after lock failures Fix issue with task cleanup after retry Change-Id: Id987043c8a26bd3f69fb4bd5b84591ae20cb83ba
| | | | * Call retryDone() when giving up after lock failuresv2.16.28upstream/stable-2.16Martin Fick2021-02-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously when giving up after retrying due to too many lock failures, a 'replication start --wait' command would wait indefinitely if it was waiting on the push that gave up. Fix this by calling retryDone() after giving up which will trigger the ReplicationStatus to reflect a failure allowing the waiting to complete. Change-Id: I0debade83612eb7ce51bab0191ab99464a6e7cd3
| | | | * Fix issue with task cleanup after retryMarcin Czech2021-02-244-14/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Destination.notifyFinished method calls finish on ReplicationTasksStorage.Task objects which are not scheduled for retry. The issue is that for rescheduled tasks PushOne.isRetrying will always returns true even if task is already replicated. That creates a situation where tasks scheduled for retry are never cleaned up. Bug: Issue 12754 Change-Id: I4b10c2752da6aa7444f57c3ce4ab70eb00c3f14e
* | | | | Merge branch 'stable-3.2' into stable-3.3Kaushik Lingarkar2021-01-251-15/+16
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: Use volatile and AtomicIntegers to be thread safe Change-Id: I7183e546b46e17530024cf4368edbd1d32216549
| * | | | Merge branch 'stable-3.1' into stable-3.2Kaushik Lingarkar2021-01-251-15/+16
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.1: Use volatile and AtomicIntegers to be thread safe Change-Id: I923730a525fbffb4c304ab0d23b088f5e8bfa307
| | * | | Merge branch 'stable-3.0' into stable-3.1Kaushik Lingarkar2021-01-251-15/+16
| | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.0: Use volatile and AtomicIntegers to be thread safe Change-Id: I0be6a13344043a48f2fc4a0367559f5b5f1fbca9
| | | * | Merge branch 'stable-2.16' into stable-3.0Kaushik Lingarkar2021-01-251-15/+16
| | | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-2.16: Use volatile and AtomicIntegers to be thread safe Change-Id: I90a3e17e2f49d07707409ba390c0a6dd0501b512
| | | | * Use volatile and AtomicIntegers to be thread safev2.16.27Adithya Chakilam2021-01-151-15/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Modify the fields in ReplicationState class to be volatile and AtomicIntegers so that changes to them are reflected to other threads. By not doing so, modifications made by one thread to these fields may not be reflected instantly depending on cpu caching thus resulting in incorrect state Change-Id: I76512b17c19cc68e4f1e6a5223899f9a184bb549
* | | | | Merge branch 'stable-3.2' into stable-3.3v3.3.2Sven Selberg2021-01-141-0/+6
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: Document that authGroup must have Access Database Change-Id: I6d7292dd7e604edbf4e2fd6b3c1615f43c1d1df4
| * | | | Merge branch 'stable-3.1' into stable-3.2v3.2.7Sven Selberg2021-01-141-0/+6
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.1: Document that authGroup must have Access Database Change-Id: I09378f4288fd1335932bdf120bba8418fc8f51c7
| | * | | Document that authGroup must have Access Databasev3.1.12Sven Selberg2021-01-141-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | Bug: Issue 13786 Change-Id: Iaf65252b25b9c40e5cfd1ac25d55fbf70536f83e
* | | | | Merge branch 'stable-3.2' into stable-3.3Antonio Barone2021-01-072-6/+7
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: Split integration tests to different targets Don't check read permission when authgroup isn't set Change-Id: I4a1e1be5c4323de1554091786c55ca9a84d391e5
| * | | | Merge branch 'stable-3.1' into stable-3.2Antonio Barone2021-01-072-6/+7
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.1: Split integration tests to different targets Don't check read permission when authgroup isn't set Change-Id: Ic5c8f0468869476a01923b4d374f0188c271daf2
| | * | | Split integration tests to different targetsAntonio Barone2021-01-071-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Running all integration tests as part of one single 'replication_it' target does not cope well with the addition of extra tests, because it is bound to take longer and longer, eventually hitting any test timeout threshold. Splitting integration tests into different targets avoids timeout failures and also provides additional benefits, such as: - Better understanding of test failures - More efficient utilization of bazel build outputs and remote caching, effectively making tests execution faster. Bug: Issue 13909 Change-Id: Ifc6cce9996d3a8a23ec2a66c377978205fb6680f
| | * | | Don't check read permission when authgroup isn't setSven Selberg2020-12-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's unnecessary to check read permission when authGroup isn't set since the then the user is a RemoteSiteUser that is-an InternalUser that has read access to everything. Change-Id: Ie6985250b0acb50c08fdcae75cc608222b1add35
* | | | | Revert "Adjust to changes in Gerrit core"Patrick Hiesel2021-01-071-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Revert submission 283559-currentuser-remove-cache-key Reason for revert: Causes a latency regression for some hosts Reverted Changes: I76bfd3ebc:Adjust to changes in Gerrit core If7ccfd9a4:Remove unused CurrentUser#cacheKey method I1378ad083:Remove PerThreadCache Change-Id: I84965f655d62c258c226ad5d585cee24dea047cc (cherry picked from commit a6a6ec5982e41a0ee9bfe24a46be96d4f13fcaaa)
* | | | | Rely on WaitUtil moved to the acceptance frameworkv3.3.1Luca Milanesio2020-12-166-74/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WaitUtil has been moved to the acceptance framework in Gerrit core. Depends-On: https://gerrit-review.googlesource.com/c/gerrit/+/291229 Change-Id: I3a31335c7878a9e5b9082d6685b860e8e6c42325
* | | | | Merge branch 'stable-3.2' into stable-3.3Nasser Grainawi2020-12-074-27/+58
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: Fix replication to retry on lock errors Change-Id: Iab364714135d693e011e8abbf7782ae620d009c4
| * | | | Merge branch 'stable-3.1' into stable-3.2v3.2.6Nasser Grainawi2020-12-074-27/+58
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.1: Fix replication to retry on lock errors Change-Id: Icacd9095feaefd240803405c5b0a16cc0b3a9ed8
| | * | | Merge branch 'stable-3.0' into stable-3.1v3.1.11Nasser Grainawi2020-12-074-27/+60
| | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.0: Fix replication to retry on lock errors Change-Id: Ib4b2c1fcac5da6551f72bce68a101b93e9b43b19
| | | * | Merge branch 'stable-2.16' into stable-3.0Nasser Grainawi2020-12-074-27/+60
| | | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-2.16: Fix replication to retry on lock errors Change-Id: I6e262d2c22d2dcd49b341b3c752d6d8b6c93b32c
| | | | * Fix replication to retry on lock errorsv3.0.16v2.16.26Kaushik Lingarkar2020-12-024-27/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Versions of Git released since 2014 have created a new status "failed to update ref" which replaces the two statuses "failed to lock" and "failed to write". So, we now see the newer status when the remote is unable to lock a ref. Refer Git commit: https://github.com/git/git/commit/6629ea2d4a5faa0a84367f6d4aedba53cb0f26b4 Config 'lockErrorMaxRetries' is not removed as part of this change as folks who have it configured currently don't run into unexpected behavior with retries when they upgrade to a newer version of the plugin. Also, the "failed to lock" check is not removed for folks still using a version of Git older than 2014. Change-Id: I9b3b15bebd55df30cbee50a0e0c2190d04f2f443
* | | | | Remove dependency on commons-io libraryDavid Ostrovsky2020-12-032-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This dependency was added in Id12780948a4 to support remoteNameStyle "basenameOnly". The only reason for this dependency is to translate project name from "foo/bar/myrepo" to myrepo. It seems to be overkill to add 169 KB to the plugin distribution for one single method. Another disadvantage is that the version of common-io library used for this is 2.2 from 2012. If gerrit installation site is using some other plugins in addition to replication plugin, then it can easily lead to classpath collision, when different versions of commons-io libraries are included as transitive dependencies of different plugins. To rectify, use a replacement method from guava library. Change-Id: Id254dc38831832a9855bd204e4c2129ec64b88ae
* | | | | Merge branch 'stable-3.2' into stable-3.3v3.3.0-rc7v3.3.0Marco Miller2020-11-231-4/+2
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: CreateProjectTask: Apply google-java formatting Change-Id: I34dd8301c2b9fcb2a8e10964c5b8d5d448227b6a
| * | | | CreateProjectTask: Apply google-java formattingMarco Miller2020-11-231-4/+2
| | | | | | | | | | | | | | | | | | | | Change-Id: If60ee5fa5297a11f8f685fefb61ad80e8f3c2990
* | | | | Merge branch 'stable-3.2' into stable-3.3Nasser Grainawi2020-11-203-20/+17
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: CreateProjectTask.java: use interface instead of implementation ReplicationQueue: Remove unused isPersisted param PushOne: Don't call delta.add(ref) twice Change-Id: Idcffd9873cbc70c6aad9ed9a0e76233494c93444
| * | | | CreateProjectTask.java: use interface instead of implementationv3.2.5.1Jacek Centkowski2020-11-051-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ReplicationDestinations interface should be used in CreateProjectTask so that specific implementation can be materialized by Guice (DI). Change-Id: If7cb21adff5c3feeeea7568c504e8e37d5c08f9e
| * | | | ReplicationQueue: Remove unused isPersisted paramNasser Grainawi2020-11-021-15/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since Ie83763e4a9fe13522f356b569fc2360fa5883224, all callers set this to false. Change-Id: I38a8a31853f5d2bc3b292b49bd050bc34f6408fe
| * | | | PushOne: Don't call delta.add(ref) twiceNasser Grainawi2020-11-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is already called as part of the condition, it doesn't need to be called again inside the body. Change-Id: Ieb11f738534ed01d09125ac6ef325ee472cb0b44
* | | | | ReplicationTasksStorage: Handle empty task filesv3.3.0-rc6v3.3.0-rc5v3.3.0-rc4Nasser Grainawi2020-11-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of NPEing if we manage to read a task file that's empty, return an empty Optional. Running the IT tests 1000 times produced this as the only failure (and only once). Change-Id: I3e7392dfb179795348d7f4a207102aa867aed85b
* | | | | Merge branch 'stable-3.2' into stable-3.3Nasser Grainawi2020-10-3010-522/+1151
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.2: (23 commits) Move shouldCleanupBothTasksAndLocks* ITs to ReplicationStorageIT ReplicationStorageIT: Wait for all pushes without order Replication*IT: Share getRef method ReplicationFanoutIT: Share setReplicationDestination ReplicationFanoutIT: Split shouldReplicateNewBranch tests ReplicationFanoutIT: Remove generic waitUntil helper ReplicationFanoutIT: Inherit from ReplicationDaemon ReplicationFanoutIT: Refactor setRemoteReplicationDestination ReplicationFanoutIT: Rename setReplicationDestination ReplicationFanoutIT: Cleanup shouldCreateIndividualReplicationTasksForEveryRemoteUrlPair Move shouldCleanupTasksAfterNewProjectReplication test Fix documentation issue Move storage portion of replicateBranchDeletion ITs Refactor Replication*IT tests to share a base class ReplicationIT: Add shouldMatch* e2e tests ReplicationStorageIT: Move shouldMatch* tests from ReplicationIT ReplicationTasksStorage: Add multi-primary unit tests ReplicationTasksStorage: Add multi-primary unit tests ReplicationStorageIT: Add shouldFire*ChangeRefs tests Move storage-based ITs into ReplicationStorageIT ... Change-Id: I81a167ccb77738984069d9433fde75ee7cf06c8e
| * | | | Move shouldCleanupBothTasksAndLocks* ITs to ReplicationStorageITNasser Grainawi2020-10-302-105/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These tests are focused on verifying storage functionality. Improve them slightly to use the best practices from ReplicationStorageIT. Change-Id: I66cf87e63c88f040d328793012a4dbf4de7e031e
| * | | | Merge branch 'stable-3.1' into stable-3.2Nasser Grainawi2020-10-309-418/+1061
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.1: ReplicationStorageIT: Wait for all pushes without order Replication*IT: Share getRef method ReplicationFanoutIT: Share setReplicationDestination ReplicationFanoutIT: Split shouldReplicateNewBranch tests ReplicationFanoutIT: Remove generic waitUntil helper ReplicationFanoutIT: Inherit from ReplicationDaemon ReplicationFanoutIT: Refactor setRemoteReplicationDestination ReplicationFanoutIT: Rename setReplicationDestination ReplicationFanoutIT: Cleanup shouldCreateIndividualReplicationTasksForEveryRemoteUrlPair Move shouldCleanupTasksAfterNewProjectReplication test Move storage portion of replicateBranchDeletion ITs Refactor Replication*IT tests to share a base class ReplicationIT: Add shouldMatch* e2e tests ReplicationStorageIT: Move shouldMatch* tests from ReplicationIT ReplicationTasksStorage: Add multi-primary unit tests ReplicationTasksStorage: Add multi-primary unit tests ReplicationStorageIT: Add shouldFire*ChangeRefs tests Move storage-based ITs into ReplicationStorageIT ReplicationTasksStorage.Task: Add multi-primary unit tests ReplicationQueue: Remove unused method Cleanup specific to stable-3.2 will be done in follow-up changes. Change-Id: Ib938c661158e8f7a3434010187b87c79e81a01b8
| | * | | Merge branch 'stable-3.0' into stable-3.1Nasser Grainawi2020-10-303-5/+47
| | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-3.0: ReplicationStorageIT: Wait for all pushes without order ReplicationTasksStorage: Add multi-primary unit tests Change-Id: I3961368f7bcf7d4aa923d07f7f89beeaaeb307d3
| | | * | Merge branch 'stable-2.16' into stable-3.0Nasser Grainawi2020-10-304-6/+116
| | | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * stable-2.16: ReplicationStorageIT: Wait for all pushes without order ReplicationTasksStorage: Add multi-primary unit tests Change-Id: I1d749621c189ee2e49f092ddc7558f83e508411f
| | | | * ReplicationStorageIT: Wait for all pushes without orderNasser Grainawi2020-10-302-4/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some tests don't have a predefined order for which events will be replicated first. Using a timeout based on a single replication event is flawed when we don't know the expected order. Instead, use a timeout for the group of events and ignore the order. For two events replicating to a single remote with a single thread, we expect the complete replication to take twice as long. Two events replicating to two remotes will use one thread each and therefore not take any longer than the single remote case. Change-Id: Ieb21b7eee32105eab5b5a15a35159bb4a837e363
| | | | * Merge "ReplicationTasksStorage: Add multi-primary unit tests" into stable-2.16v2.16.23Martin Fick2020-10-282-2/+78
| | | | |\
| | | | | * ReplicationTasksStorage: Add multi-primary unit testsAdithya Chakilam2020-10-262-2/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These tests examine the replication scenarios under multi-primary setup making use of the api calls present in ReplicationTasksStorage class similarly as done in single primary setup. These tests ensure that the replication compatibility in multi-primary setup is not broken. Change-Id: I375b731829f3c0640d3a7a98635e1e5c526908ca
| | * | | | Merge "ReplicationTasksStorage.Task: Add multi-primary unit tests" into ↵Martin Fick2020-10-302-6/+200
| | |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | stable-3.1
| | | * | | | ReplicationTasksStorage.Task: Add multi-primary unit testsAdithya Chakilam2020-10-132-6/+200
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These tests examine the replication scenarios under multi-primary setup making use of the api calls present in ReplicationTasksStorage.Task class similarly as done in single master setup. These tests ensure that the replication compatability in multi-primary setup is not broken. Change-Id: I980e8286bf11d31c6ab89e49ef065fdde1118181
| | * | | | | Replication*IT: Share getRef methodNasser Grainawi2020-10-283-8/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helper is common to a couple test classes, so share it. Change-Id: I5839c31ad734c384e812e9e1c7bcba8ba05c23cc
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-24 20:32:35 +0000