Upgrade mongodb driver from 1.14.0 to 1.17.4

[shmsr]

Describe the enhancement: Upgrade go.mongodb.org/mongo-driver from 1.14.0 to latest 1.17.4 (1.x); mongodb/mongo-go-driver@v1.14.0...v1.17.4

Describe a specific use case for the enhancement or feature: Better to stay updated and stay up to date with latest bug fixes and improvements.

[shmsr]

We have identified the root cause of the connection leak issue affecting stack versions 8.16.x and higher (including 8.17.x and later).

Root Cause Analysis

Our MongoDB module uses the official MongoDB's Go driver (go.mongodb.org/mongo-driver). During the upgrade to stack 8.16.x, we upgraded this driver (indirectly) from v1.5.1 to v1.14.0. Unfortunately, v1.14.0 contains a known connection leak bug that was introduced in v1.13.1.

Issue Details:

• The connection leak occurs during client disconnection operations
• Over time, "ESTABLISHED" connections accumulate without being properly closed
• This eventually leads to open file limit exhaustion after repeated Fetch operations

References:

• MongoDB Go Driver 1.14.1 Release Announcement (clear mention of the "Connection leak" bug.
• https://github.com/mongodb/mongo-go-driver/releases/tag/v1.14.1
• JIRA Issue: GODRIVER-3107

Solution

We are upgrading the MongoDB Go driver to v1.17.4, which includes:

• The connection leak fix
• Additional connection handling reliability improvements

We also have done extensive testing of around 1h+ confirming no connection leaks after upgrading the library.

Release Timeline

The fix will be included in:

• 8.17.8 (backport)
• 8.18.3 (backport)
• 9.0.3 (backport)
• All future stack releases

Recommendation

We strongly recommend upgrading to one of the fixed stack versions listed above (when they are available) to resolve this issue.

[shmsr]

@mykola-elastic I am quickly creating a PR for this. Would need your help with reviewing and also reviewing the backports. The fix is urgent that needs to be available in 8.17.x, 8.18.x, 9.0.x, and all future releases.