Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event hub service call will not retry if that got failed - APIM 4.0.0 #1920

Closed
Sumudu-Sahan opened this issue Jun 14, 2023 · 0 comments
Closed

Comments

@Sumudu-Sahan
Copy link

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

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants