Skip to content

DOCSP-30349: server selection errors #548

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.

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

Merged
merged 6 commits into from
Jun 3, 2024
Merged
Changes from 2 commits
Commits
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
37 changes: 37 additions & 0 deletions source/connection-troubleshooting.txt
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,43 @@ Consider setting ``maxConnectionLifeTime`` and
maintains a connection to a MongoDB instance. For more information about these
parameters, see :ref:`Connection Pool Settings <mcs-connectionpool-settings>`.

.. _java-server-selection-errors:

Server Selection Errors
-----------------------

MongoDB might not be able to complete a request even when some servers
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
MongoDB might not be able to complete a request even when some servers
Your application might not be able to complete a request even when some servers

are available, causing the driver to return a server selection error.
The following list describes some situations in which you
might encounter a server selection error:

- You use tag sets in a read preference specification when no server
with those tags exists.
- You write to a replica set when the primary node is unavailable.

This error is of type ``MongoTimeoutException``. The following code
shows a sample of the exception that occurs if you attempt to send a
request to a replica set without a primary:

.. code-block:: none

com.mongodb.MongoTimeoutException: Timed out after 30000 ms while
waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}.

Client view of cluster state is {type=REPLICA_SET, servers=[
{address=node01:27017, type=UNKNOWN, state=DISCONNECTED},
{address=node02:27017, type=REPLICA_SET_SECONDARY, roundTripTime=..., state=CONNECTED},
{address=node03:27017, type=REPLICA_SET_SECONDARY, roundTripTime=..., state=CONNECTED}
];

The error includes a view of the cluster state that describes the
connection state of each node. In the preceding error, the only
connected servers are secondary nodes, ``node02`` and ``node03``. Thus,
the request times out as MongoDB is unable to select a server that
satisfies the read preference of ``primary``. In this situation, reads
can still be sent to the connected secondary nodes if you set the read
preference to ``secondary``, ``secondaryPreferred``, or ``nearest``.

.. _java-miscellaneous-errors:

Miscellaneous Errors
Expand Down
Loading