Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-711

Change in behavior on keepAlive

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.1.8
    • Component/s: None
    • Labels:

      Previously, the guidance on keepAlive was that we should set socketOptions.keepAlive : 0 in order to enable keepAlive and that would also set keepAliveInitialDelay to 0. In a recent change this was altered, now keepAlive is only set to true if keepAlive is > 0. That would mean everyone out there which was previously using keepAlive : 0 is now no longer using keepAlive (because 0 is not > 0).

      Was that change meant to be a change in driver configuration. As recently as December the current suggestion was to set keepAlive : 0 to enable keepAlive see https://jira.mongodb.org/browse/NODE-614 . If it's an accident it should probably be reverted, if it's intentional you may want to call out that the setting changed and the docs should be updated to account.

            Assignee:
            christkv Christian Amor Kvalheim
            Reporter:
            owenallenaz Owen Allen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: