What implications would a lagging sync interval have over failover/relocate actions? 

Assuming sync is delayed and there is a need to failover/relocate what options does the user have? 

Do we stop users from performing failover/relocate, is it even possible to stop users? Could they correct things before proceeding to perform failover/relocate? 

In case we allow users to continue with failover by displaying a warning what outcomes could users expect to see after the actions complete?

(In reply to Chandan from comment #14)
> What implications would a lagging sync interval have over failover/relocate
> actions? 
> 
> Assuming sync is delayed and there is a need to failover/relocate what
> options does the user have? 
> 
> Do we stop users from performing failover/relocate, is it even possible to
> stop users? Could they correct things before proceeding to perform
> failover/relocate? 
> 
> In case we allow users to continue with failover by displaying a warning
> what outcomes could users expect to see after the actions complete?

Feel free to setup a meeting and include all required stakeholders to discuss further.

(In reply to Chandan from comment #14)
> What implications would a lagging sync interval have over failover/relocate
> actions? 
> 
> Assuming sync is delayed and there is a need to failover/relocate what
> options does the user have? 
> 
> Do we stop users from performing failover/relocate, is it even possible to
> stop users? Could they correct things before proceeding to perform
> failover/relocate? 
> 
> In case we allow users to continue with failover by displaying a warning
> what outcomes could users expect to see after the actions complete?

Adding more the Chandan doubts:
  - We are also supporting CLI-based implementation, What if the user trigger failover/relocates from CLI? 
  - Assume this sync delay is happening and After some time cluster is down, User dont have a choice other than failover, how does this dialogue box will help?