jdeppe-pivotal commented on a change in pull request #7328:
URL: https://github.com/apache/geode/pull/7328#discussion_r796189373
##########
File path:
geode-for-redis/src/distributedTest/java/org/apache/geode/redis/internal/commands/executor/key/RenameDUnitTest.java
##########
@@ -210,6 +227,48 @@ private void doConcurrentRenames(List<String> listOfKeys1,
List<String> listOfKe
future4.get();
}
+ @Test
+ public void givenCrashDuringRename_thenDoesNotLeaveInconsistencies() throws
Exception {
+ final AtomicBoolean running = new AtomicBoolean(true);
+
+ final List<String> hashtags = new ArrayList<>();
+ hashtags.add(clusterStartUp.getKeyOnServer("rename", 1));
+ hashtags.add(clusterStartUp.getKeyOnServer("rename", 2));
+ hashtags.add(clusterStartUp.getKeyOnServer("rename", 3));
+
+ final Runnable task1 = () -> renamePerformAndVerify(1, 10000,
hashtags.get(0), running, true);
+ final Runnable task2 = () -> renamePerformAndVerify(2, 10000,
hashtags.get(1), running, true);
+ final Runnable task3 = () -> renamePerformAndVerify(3, 10000,
hashtags.get(2), running, true);
+
+ final Future<Void> future1 = executor.runAsync(task1);
+ final Future<Void> future2 = executor.runAsync(task2);
+ final Future<Void> future3 = executor.runAsync(task3);
+
+ final String finalRedisPort = Integer.toString(server3Port);
+ final int finalLocatorPort = locatorPort;
+ final Future<?> crasherFuture = executor.submit(() -> {
+ try {
+ for (int i = 0; i < 20 && running.get(); i++) {
+ clusterStartUp.moveBucketForKey(hashtags.get(0), "server-3");
Review comment:
The point was to always ensure we're crashing the server that actually
has the key. It seems easier to move the bucket (key) to a known server and
then do the stop/start instead of figuring out which server is hosting the key
and then perform the stop/start against a varying server.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
