Skip to content

Commit a99d8e1

Browse files
authored
Merge pull request #92802 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
2 parents d48403d + 9057cb7 commit a99d8e1

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

articles/cosmos-db/create-mongodb-nodejs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Run the following commands to clone the sample repository. This sample repositor
5050
1. Open a command prompt, create a new folder named git-samples, then close the command prompt.
5151

5252
```bash
53-
md "C:\git-samples"
53+
mkdir "C:\git-samples"
5454
```
5555

5656
2. Open a git terminal window, such as git bash, and use the `cd` command to change to the new folder to install the sample app.

articles/traffic-manager/traffic-manager-FAQs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -413,7 +413,10 @@ Yes. You can specify TCP as the monitoring protocol and Traffic Manager can init
413413

414414
### What specific responses are required from the endpoint when using TCP monitoring?
415415

416-
When TCP monitoring is used, Traffic Manager starts a three-way TCP handshake by sending a SYN request to endpoint at the specified port. It then waits for a period of time (as specified in the timeout settings) for a response from the endpoint. If the endpoint responds to the SYN request with a SYN-ACK response within the timeout period specified in the monitoring settings, then that endpoint is considered healthy. If the SYN-ACK response is received, the Traffic Manager resets the connection by responding back with a RST.
416+
When TCP monitoring is used, Traffic Manager starts a three-way TCP handshake by sending a SYN request to endpoint at the specified port. It then waits for a SYN-ACK response from the endpoint for a period of time (specified in the timeout settings).
417+
418+
- If a SYN-ACK response is received within the timeout period specified in the monitoring settings, then that endpoint is considered healthy. A FIN or FIN-ACK is the expected response from the Traffic Manager when it regularly terminates a socket.
419+
- If a SYN-ACK response is received after the specified timeout, the Traffic Manager will respond with an RST to reset the connection.
417420

418421
### How fast does Traffic Manager move my users away from an unhealthy endpoint?
419422

0 commit comments

Comments
 (0)