Cluster resource management is delayed after a node is fenced due to a resource failure in a RHEL 7 High Availability cluster

Issue

• We have a high token setting in our cluster, and whenever a node gets fenced due to a resource failure, the cluster blocks for a long time before resuming activity. The delay seems to be waiting for that token timeout, when eventually corosync processes a membership change and activity resumes.
• Cluster doesn't recover any resources for a period of time after a node gets fenced due to failing a resource op
• I see my cluster resource sitting failed/stopped when a node gets fenced after a stop failure, and doesn't get recovered for a few minutes.