Skip to content

Conversation

@rkistner
Copy link
Contributor

For testing MongoDB connections, we use a relatively short connection timeout (specifically serverSelectionTimeoutMS), since that is the only way to detect clusters we cannot connect to due to IP access list issues. However, the timeout of 1000ms was too short when connecting to a cluster in for example AWS ap-southeast-2, from our test node in us-east-1.

This increases the timeout sufficiently to cover these cases.

@changeset-bot
Copy link

changeset-bot bot commented Mar 17, 2025

🦋 Changeset detected

Latest commit: 6ba28af

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages
Name Type
@powersync/service-module-mongodb Patch
@powersync/service-image Patch
@powersync/service-core Patch
@powersync/service-core-tests Patch
@powersync/service-module-mongodb-storage Patch
@powersync/service-module-mysql Patch
@powersync/service-module-postgres-storage Patch
@powersync/service-module-postgres Patch
test-client Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@rkistner rkistner requested a review from stevensJourney March 17, 2025 07:34
@rkistner rkistner merged commit 535e708 into main Mar 17, 2025
21 checks passed
@rkistner rkistner deleted the fix-test-connection-timeout branch March 17, 2025 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants