question

SfDen-4602 avatar image
0 Votes"
SfDen-4602 asked prmanhas-MSFT edited

Liveness probe - breaks port redirection on node

I have standalone cluster 7.1.417.9590 on Windows Server 2019 and containerized application.
I add Liveness probe in ApplicationManifest - https://docs.microsoft.com/en-us/azure/service-fabric/probes-codepackage
<CodePackagePolicy CodePackageRef="Code">
<Probes>
<Probe Type="Liveness" FailureThreshold="3" SuccessThreshold="2" InitialDelaySeconds="10" PeriodSeconds="5" TimeoutSeconds="5">
<HttpGet Path="/healthcheck" Port="2532" Scheme="http"/>
</Probe>
</Probes>
</CodePackagePolicy>
Application successfully upgrade, but http endpoint becomes unavailable. I tested this on several applications.

azure-service-fabricservice-fabric-standalone
· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SfDen-4602 Have you had a chance to look at the report for your container

I’m suspecting that tour probe isn’t working which is causing your container to restart making it’s normal http endpoint unavailable

Try to use another probe type maybe using TCP, etc.

0 Votes 0 ·

Health State my container - OK.
Http Liveness probe works properly. If i'm manually, from container, closed http endpoint, then container restarted, as expected.
Container endpoint available:
Test-NetConnection -ComputerName <ContainerIP> -port 2532
True

Node endpoint unavailable:
Test-NetConnection -ComputerName <NodeIP> -port 2532
False
Without Liveness probe all it`s OK

0 Votes 0 ·

@SfDen-4602 Thank you for your response.

Can you help me understand what is the current issue you are facing?

0 Votes 0 ·
Show more comments

0 Answers