Python client error handling when server goes down

We had recently encountered an issue in our QA cluster(single node cluster) where a node had gone down and we encountered the following issue while trying to write to the server: Error: (-1, 'Invalid node for key.'). On bringing the node back up, we went ahead and restarted all our QA application nodes.

Since we did not get to see if the python client actually responds to the aerospike server being brought back up, we wanted to know as general guidance if the python client is responsive enough that it will automatically connect to the server once the server is brought up after a potential aerospike server downtime!

Good question!

As long as the Python client has successfully connected before the cluster went down, it should automatically reconnect to the cluster when it comes back up.