Use next available port when the default port is already used #2682
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PramodValavala-MSFT
requested review from
AnatoliB and
michaelpeng36
as code owners
|
@kshyju I noticed you flagged this for discussion, have you looked into this further? |
| } | ||
| startPort++; | ||
| } | ||
|
|
There was a problem hiding this comment.
What if all ports are exhausted, then should we log the errors?
There was a problem hiding this comment.
After checking the ports after the start port, the GetAvailablePort method will try to get any available port at random.
|
@PramodValavala-MSFT thank you for the contribution, can you please address the PR feedback? |
PramodValavala-MSFT
force-pushed
the
use-next-available-port
branch
from
86ac64b to
116c009
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When working with multiple function apps locally, every function host apart from the first needs to have a different port manually set either via the command line argument
--portor theHost.LocalHttpPortproperty inlocal.settings.json. Also, in some cases the default port might be blocked with another process (sometimes an olderfuncitself that didn't terminate).This PR adds support to pick up the next available port (7072, 7073, ...) when none is provided. If a port is defined in either place mentioned above, this would not do anything.
One known issue is that multiple function apps run at the exact same time might end up picking the same port, causing one of them to error out. This is present even today with the static default port, primarily because the validation is done before the host starts up.