orleans cluster problem

[wz172]

I used Adonet as the cluster table, created two different Silo A and B, and according to the official documentation, both clusters were able to start and work properly.But I had a tricky problem.There is no graceful exit of SiloA, the state in the cluster is active at that time, now I want to start SiloB, I got some errors during startup, and finally the program exited abnormally, because silo abnormal exit factors are not controllable (l example: server power failure), what can be done to deal with this problem?

Can we use the start write IAmAliveTime time as the auxiliary judgment condition? Or make a policy in the configuration cluster, whether to use the newly added silo host as the centralized state, or to ensure that the old cluster silo host is the primary state of the cluster.

Thank you very much for your answer

[wz172]

Can someone help?

[luckyycode]

In case of AdoNet provider I had to slightly edit the existing implementation and replace it in service container It was about defunct silo removal, it was our dirty approach but it worked, taking about 3.6.x versions

But right now I got the same type of a problem in Orleans 7 with consul though you may need three of silos for quorum I guess?