@Test
    public void testPersistentFailureOldClusterState() {
        runSimulation("First correctnode .*, wrongnode .*, downnode .*, worked .*, failed .* "
                    + "Last correctnode 100, wrongnode 0, downnode 0, worked 100, failed 0",
                      new PersistentFailureTestParameters().addBadNode(new BadNode(3, FailureType.OLD_CLUSTER_STATE).setDownInCurrentState()));
    }
Verify that a node responding with old cluster state doesn't ruin overall performance (By dumping/switching cached
state too often)
Let one node reporting an old cluster state (but node is still set up in fleetcontroller state).
We expect some requests to go to wrong node due to this issue, but the majority of requests should be unaffected.
documentapi/src/test/java/com/yahoo/documentapi/messagebus/protocol/test/storagepolicy/ContentPolicyTest.java