Tests in this folder implicitly assume that SDAM heartbeats are not involved even though some tests mention SDAM hello requests in the description. If SDAM requests is started, it may lead to flaky test results since we don't have control over who runs hello first. If SDAM catchs the configured failpoint for hello first, it can just clear the pool which in turn mean that the pool is in unexpected state even before test itself is started