What else to do when a context is cancelled?

[shreemaan-abhishek]

Currently, we just close the etcd client by calling client.Close() this revokes the lease which means that the current instance is no longer participating in the leader election. If there are other instances/replicas of this program/process, they can proceed to take ownership of the lease under the given prefix to claim leadership.

Calling cli.Close() causes the process to busy-wait. (fancy word for doing nothing). I noticed this when I used Rasputin in a simple command line app. Not sure if busy-waiting can be harmful when Rasputin is used in kubernetes microservices. Just creating this issue to document this thought.

[shreemaan-abhishek]

Another thing:

On this line, if we use log.Fatal() instead of log.Println() (or other similar logging methods) the process ends. (Again, this was noticed when using Rasputin in a command line app)