Hi
I had a similear issue but I resolved it by connecting to the secondary node and do a rollback of the configuration. I belive it's a better way of solving it than commit synchronize force. In my case it solved the issue. I have created a blogpost on it here: https://networksandrants.wordpress.com/2016/04/10/secondary-node-locked-when-commiting/