@Test
    public void testPersistentFailureResetClusterStateNoGoodNodes() {
        // If reset detection works (within the few messages sent in test), we should not fail any requests in second half.

        // Current problem here, is that even though we from time to time will send requests to other nodes, and will eventually throw the faulty cluster state,
        // we will have pending operations towards this distributor when it happens, so it very quickly returns into a bad state.

        // This issue should hopefully not be that critical as we don't expect nodes to stay up and report erronious states. Even nodes that are down do get the
        // cluster states sent to them, and if that doesn't work, how do the client manage to talk to them?

        runSimulation("First correctnode .*, wrongnode .*, downnode .*, worked .*, failed .* "
                    + "Last correctnode .*, wrongnode 100, downnode 100, worked 0, failed 100",
                      new PersistentFailureTestParameters().addBadNode(new BadNode(3, FailureType.RESET_CLUSTER_STATE_NO_GOOD_NODES).setDownInCurrentState()));
    }
Verify that a reset cluster state version doesn't keep sending requests to the wrong node.
We expect a few failures in first half. We should have detected the issue before second half, so there all should be fine.
documentapi/src/test/java/com/yahoo/documentapi/messagebus/protocol/test/storagepolicy/ContentPolicyTest.java