Configuring Rate limiting in Active Active deployment
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
When configuring rate limiting [1] in active-active deployment, it would be great if we could add a more clear explanation regarding the reason for configuring the node 2 hostname as the event_duplicate_url under the [apim.throttling] section.
Also regarding the throttle_decision_endpoints parameter, it would be great if we can add more clear explanation of how to configure this parameter in control plane nodes when deploying API Manager in a Kubernetes environment.
[1] https://apim.docs.wso2.com/en/4.1.0/install-and-setup/setup/single-node/configuring-an-active-active-deployment/#step-8-configure-rate-limiting
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked Active-Active deployment documentation and review the “Step 8: Configure rate limiting” section. Read the existing guidance for event_duplicate_url under apim.throttling and throttle_decision_endpoints in Kubernetes control-plane deployments. Done means the page clearly explains the node 2 hostname requirement and how to configure the endpoint parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100