You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the TM node got started up before the CP node starting up, all the deployed throttling policies got undeployed and the TM will not retry the event hub service call to retrieve policies from the CP node.
Steps to Reproduce
Configured a distributed deployment with a separate TM node. (However, we don't need a GW in this case)
Started all the nodes.
Check the <TM_HOME>/repository/deployment/server/executionplans directory and able to see all the execution plans are there.
Then stopped all the nodes.
Started the traffic manager without starting the CP node.
Able to see that all the execution plans inside the <TM_HOME>/repository/deployment/server/executionplans directory got removed except the RequestPreProcessorExecutionPlan.siddhiql file.
After starting up the TM node and when starting up the control plane node, not able to see any retry calls from the traffic manager to the event hub service call to retrieve policies.
Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Description
If the TM node got started up before the CP node starting up, all the deployed throttling policies got undeployed and the TM will not retry the event hub service call to retrieve policies from the CP node.
Steps to Reproduce
Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: