Configuration commited successfully when secondary was active.
But while pushing configuration to the device group, it was taking longer time. Stuck at 50% for few device group and for some, commit was showing at 0% for 4 to 5 minutes, after that percentage started increasing.
So total duration to push is in between 10 to 15 minutes
But when primary was active configuration was pushed within less time about 2 to 3 minutes.
If it is known issue, please let me share your suggestion.
That's certainly not a known issue or expected behavior. It's possible that the system was already running a lot of jobs and simply couldn't queue these as quick as you are used to, but either way if you continue to see this behavior I would log a case with TAC so they can actually review logs. The system should behave exactly the same regardless of which node is active.
Just in case check this article https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm1CCAS and CPU and memory of the secondary panorama before and when you coomit :
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!