microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Load balance and deployment
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
I made a test with 2 recording bot instances in 2 VMs behind load balancer. I used remote debugger and I saw actions(mute/unmuted/hold etc.) will be sticked to correct instance. I could not find the code did that. When starting the call the request sometimes goes to both vms but after connected everything just in one instance properly.
Also adding more vm is not an issue but automatically scaling down seems to impact to current calls that handle by the instance. How could we make sure load balancer only removes instance if no current call in it. In addition how to deploy new version without outage or lose current calls.
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
The issue names no files, tests, or entry points. Start by reviewing the recording bot deployment and load-balancer setup, then determine how current calls are associated with instances. Done would require an agreed approach for scale-down and deploying new versions without interrupting calls.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100