Improve backup stress test for single instance

neo4j · Nov 28, 2016 · 4ade1ff · 4ade1ff
1 parent cba1fb6
commit 4ade1ff
Show file tree

Hide file tree

Showing 25 changed files with 376 additions and 366 deletions.
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
@@ -34,4 +34,4 @@ I discovered that when I mount `data/` to a volume on my host, and then stop the
 `write.lock` should be removed now.
 
 ### Actual behavior
-`write.lock` is still present and preventing access by other programs.
+`write.lock` is still present and preventing access by other programs.
diff --git a/enterprise/backup/src/test/java/org/neo4j/backup/BackupServiceIT.java b/enterprise/backup/src/test/java/org/neo4j/backup/BackupServiceIT.java
@@ -940,20 +940,6 @@ public void incrementalBackupShouldFailWhenTargetDirContainsDifferentStore() thr
         }
     }
 
-    @Test
-    public void theBackupServiceShouldBeHappyUnderStress() throws Exception
-    {
-        Callable<Integer> callable = new BackupServiceStressTestingBuilder()
-                .until( untilTimeExpired( 10, SECONDS ) )
-                .withStore( storeDir )
-                .withBackupDirectory( backupDir )
-                .withBackupAddress( BACKUP_HOST, backupPort )
-                .build();
-
-        int brokenStores = callable.call();
-        assertEquals( 0, brokenStores );
-    }
-
     private void defaultBackupPortHostParams()
     {
         dbRule.setConfig( OnlineBackupSettings.online_backup_server, BACKUP_HOST + ":" + backupPort );

diff --git a/enterprise/backup/src/test/java/org/neo4j/backup/BackupServiceStressTestingBuilder.java b/enterprise/backup/src/test/java/org/neo4j/backup/BackupServiceStressTestingBuilder.java