Hi,
As long as your chassis cluster is established properly and control probes are reaching both nodes then you should be fine. Run the following command to confirm if control plane is working fine;
# run clear chassis cluster control-plane statistics
# ...is cluster control-plane statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 3
Heartbeat packets received: 3
Heartbeat packet errors: 0
Fabric link statistics:
Probes sent: 3
Probes received: 3
Probe errors: 0
If the probes are not being recieved and sent properly then your devices may be acting out of sync.
When you log on to a device and make changes, it initially makes a copy of the configuration that is local to itself. We call it "candidate configuration". When you commit it from either node, it will try to push the candidate configuration to BOTH nodes via control link using JSRPD. Obviously if the link is broken the the configuration will only be committed to the local node only.
Let's say you had a working cluster and then you detached the nodes i.e. disconnected the control link and fabric link as well. Now both nodes are acting as primary (Split-brain). You make some minor changes to the configuration on one of the nodes. But both nodes still remain in the same cluster-id. So when you connect them back together by joining the control and fabric links then the node that becomes primary will drive the configuration. The primary node configuration will override the secondary node configuration. So no matter where you are committing from, it will be the same configuration on two devices as long as your control and fabric links are up.
Hope that helps.
Thanks
-Iqbal