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.

Sign up for GitHub

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

Jump to bottom

lb: LoadBalancingTranscoder should use AuthToken.SessionId instead of ManifestID to index into sessions #1748

Closed
yondonfu opened this issue Jan 28, 2021 · 0 comments · Fixed by #1784
Closed

lb: LoadBalancingTranscoder should use AuthToken.SessionId instead of ManifestID to index into sessions #1748

yondonfu opened this issue Jan 28, 2021 · 0 comments · Fixed by #1784
Assignees
@jailuthra
Labels
type: bug Something isn't working

Comments

@yondonfu
Copy link
Member

Describe the bug
A clear and concise description of what the bug is.

The orchestrator uses AuthToken.SessionId to index into its session map, but the LoadBalancingTranscoder still uses the ManifestID to index into sessions. As a result, two different transcode sessions with the same manifestID can result in the use of the same load balancer session when different load balancer sessions should be used.
@yondonfu yondonfu added the type: bug Something isn't working label Jan 28, 2021
@jailuthra jailuthra mentioned this issue Mar 4, 2021
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jailuthra jailuthra

Labels
type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

core/lb: use SessionID as map index livepeer/go-livepeer
2 participants
@jailuthra @yondonfu