Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

feat(NODE-3607): update faq with keepalive changes #639

Closed
wants to merge 1 commit into from
Closed

feat(NODE-3607): update faq with keepalive changes #639

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions source/faq.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,18 @@ this only works if the operating system supports ``SO_KEEPALIVE``\ .
.. warning::
If a firewall ignores or drops the ``keepAlive`` packets this may not work

.. warning::
This option is deprecated in 5.2.0 and will be removed in a future release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's wait to do this until we make a decision on mongodb/node-mongodb-native#3621 and the corresponding ticket; it may end up being easier to track via a DOCSP ticket instead

Once removed it will always be enabled with an initial delay of 300 seconds,
resulting in socket settings of:

- SO_KEEPALIVE=1
- TCP_KEEPIDLE=300000
- TCP_KEEPCNT=10
- TCP_KEEPINTVL=1



What Can I Do If I'm Experiencing Unexpected Network Behavior?
--------------------------------------------------------------
Internal firewalls that exist between application servers and MongoDB
Expand Down