Fix logic for reconnecting to new nodes · whatyouhide/xandra@4a8eb7c

test if a node goes down, the cluster removes its control connection and pool (Xandra.TestClustering.IntegrationTest)

test if a node goes down and then rejoins, the cluster readds its control connection and pool (Xandra.TestClustering.IntegrationTest)

test connect and discover peers (Xandra.TestClustering.IntegrationTest)

test nodes that go unreachable but still addressable should be removed from the pool (Xandra.TestClustering.IntegrationTest)

Process completed with exit code 1.

test if a node goes down, the cluster removes its control connection and pool (Xandra.TestClustering.IntegrationTest)

test if a node goes down and then rejoins, the cluster readds its control connection and pool (Xandra.TestClustering.IntegrationTest)

test connect and discover peers (Xandra.TestClustering.IntegrationTest)

test nodes that go unreachable but still addressable should be removed from the pool (Xandra.TestClustering.IntegrationTest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, jwalton/gh-docker-logs@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Provide feedback