Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search Sign up Reseting focus

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

This repository has been archived by the owner on Jan 16, 2021. It is now read-only.

Allowed Application Ports #160

aaneja opened this issue Feb 6, 2017 · 2 comments

Allowed Application Ports #160

aaneja opened this issue Feb 6, 2017 · 2 comments

Comments

aaneja commented Feb 6, 2017

I'm most likely reading the docs wrong. But Configure your standalone cluster states:

applicationPorts are the ports that will be used by the Service Fabric applications. These should be a subset of the ephemeralPorts, enough to cover the endpoint requirement of your applications. Service Fabric will use these whenever new ports are required, as well as take care of opening the firewall for these ports.

I noticed though that

  1. The json snippet for 'Node Types' though has:
    "applicationPorts": < "startPort": "20575", "endPort": "20605" >, "ephemeralPorts": < "startPort": "20606", "endPort": "20861" >
    The applicationPorts are not a subset of the the ephemeralPorts.
  2. This config has no bearing on the endpoints specified in my ServiceManifest.xml. If I specify an endpoint like:

    I still see on the VMSS instances that a firewall rule is added to allow traffic on port 8282.

What am I reading wrong ? How do I ensure that endpoint ports would not be blocked by service fabric and will always be open on the VM firewalls ?

The text was updated successfully, but these errors were encountered: