I have a questing regarding the failure handling when using a singleton. I did a lot of web research but didn’t find a solution yet. Perhaps someone can point me into the correct direction:
In my cluster I have a persistent singleton. When the persitence database is not available the recovery phase fails after a short time and the singleton actor is stopped. On the user side of the singleton I am doing a lookup of the singleton’s proxy using the Identity message. That works in all cases since the proxy exists even if the singleton itself does not start up or terminates. Also having a termination watch on the proxy does not provide any information since the singleton proxy itself does not terminate. How do I detect that failure situation on the user side?
I tried to add a kind of Ping message to the singleton itself. But using that approach only fills the logfiles with dead-letter messages since the singleton itself does not exist anymore and the message can not be delivered.
Is there any way for a user to detect the situation that the singleton’s proxy does not have a connection to the singlton itself anymore? I guess the singleton proxy internally must be aware of that situation …
Thanks for your help