[KAFKA-368] MongoDB source connector (>1.9.0) does not release connections Created: 09/May/23 Updated: 16/May/23 Resolved: 15/May/23 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | 1.9.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Artsiom Krauchanka | Assignee: | Valentin Kavalenka |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
Our company faced an issue after migrating to the MongoDB source connector version 1.9.0 (and higher). Description: After we migrated to version 1.9.0 (the issue appears also in all the versions up to 1.10.0), the number of connections started to grow each time MongoDB is down at night (see screenshot #2 attached). The connections are kept alive during the time and eventually, it leads to the reaching of the Atlas cluster limits. After that, our connector is not able to consume any changes from MongoDB and write to Kafka. We've tried various MongoDB Java driver configs such as connectTimeoutM, ocketTimeoutMS, maxIdleTimeMS, maxLifeTimeMS but it had no effect on the number of connections. Versions that we use:
The only difference between the 2 use cases was MongoDB Source connector (1.8.1 vs 1.9.0). |
| Comments |
| Comment by Artsiom Krauchanka [ 16/May/23 ] |
|
Thanks, valentin.kovalenko@mongodb.com, looking forward to the new version 1.10.1! |
| Comment by Valentin Kavalenka [ 15/May/23 ] |
|
Hi artsiom.krauchanka@comparethemarket.com, I believe this is a duplicate of |
| Comment by Service Account: DBX TPM [ 09/May/23 ] |
|
Hi artsiom.krauchanka@comparethemarket.com, thank you for reporting this issue! The team will look into it and get back to you soon. |