Aerospike client detecting cluster change but keep trying to contact removed node

[acaporrini]

We use the gem on version 2.29.0 to connect to an aerospike cluster.

We noticed that when a node is removed from the cluster our app keeps trying to contact that node even tho the cluster change is detected.

Example:

D, [2024-12-26T10:40:42.923364 #12312] DEBUG -- : Removing alias 23.19.49.167:3000
I, [2024-12-26T10:40:42.923904 #12312]  INFO -- : Removed node `#<Aerospike::Node:0x00007f7c493864a0>`
D, [2024-12-26T10:40:42.924504 #12312] DEBUG -- : Cluster config change detected; active nodes: [... list of nodes]
D, [2024-12-26T10:40:42.924638 #12312] DEBUG -- : Cluster features: ["batch-any", "batch-index", "blob-bits", "cdt-list", "cdt-map", "cluster-stable", "float", "geo", "sindex-exists", "peers", "pipelining", "pquery", "pscans", "query-show", "relaxed-sc", "replicas", "replicas-all", "replicas-master", "replicas-max", "truncate-namespace", "udf", "xdr"]
I, [2024-12-26T10:40:42.924842 #12312]  INFO -- : Tend finished. 1 node has left the cluster. Old node count: 16, New node count: 15

However, immediately after, keeps trying to reach out to the old node:

D, [2024-12-26T10:41:43.790549 #20634] DEBUG -- : Trying to connect to 23.19.49.167:3000 with 4s timeout
E, [2024-12-26T10:41:43.791262 #20634] ERROR -- : Node #<Aerospike::Node:0x00007fa22123b688>: Connection refused - connect(2) for 23.19.49.167:3000
D, [2024-12-26T10:41:44.291484 #20634] DEBUG -- : Trying to connect to 23.19.49.167:3000 with 4s timeout
E, [2024-12-26T10:41:44.291841 #20634] ERROR -- : Node #<Aerospike::Node:0x00007fa22123b688>: Connection refused - connect(2) for 23.19.49.167:3000
D, [2024-12-26T10:41:44.792091 #20634] DEBUG -- : Trying to connect to 23.19.49.167:3000 with 4s timeout

Why is this happening?