Skip to content

Initialize multiple language workers #4194

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Closed
pragnagopa opened this issue Mar 13, 2019 · 0 comments · Fixed by #4210
Closed

Initialize multiple language workers #4194

pragnagopa opened this issue Mar 13, 2019 · 0 comments · Fixed by #4210
Assignees
@pragnagopa
Labels
feature:language-extensibility
Milestone
Functions Sprint 49

Comments

@pragnagopa
Copy link
Member

Scenarios to handle:

  • Start one language worker

    • Handle placeholders and non placeholder languages

  • Define an AppSetting to configure number of worker processes

  • FunctionDispatcher needs to handle spinning new language workers set by the app setting.
@pragnagopa pragnagopa added this to the Functions Sprint 46 milestone Mar 13, 2019
@pragnagopa pragnagopa self-assigned this Mar 13, 2019
@pragnagopa pragnagopa mentioned this issue Mar 13, 2019
Closed
@pragnagopa pragnagopa modified the milestones: Functions Sprint 46, Triaged Mar 24, 2019
@pragnagopa pragnagopa modified the milestones: Triaged, Functions Sprint 47 Apr 3, 2019
@pragnagopa pragnagopa mentioned this issue Apr 5, 2019
Merged
@asavaritayal asavaritayal mentioned this issue May 1, 2019
Closed
@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees

@pragnagopa pragnagopa

Labels
feature:language-extensibility
Projects
None yet
Milestone
Functions Sprint 49
Development

Successfully merging a pull request may close this issue.

Multiple workers pragnagopa/azure-functions-host
2 participants
@pragnagopa @fabiocav