[DOCS-13825] [TOOLS] mongodump 4.2 error when run against MongoDB 3.4 Created: 11/Aug/20  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, tools
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Anonymous Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents TOOLS-2698 mongodump 4.2 error when run against ... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-11348

 Description   

Description

User confusion re: MongoDB compatibility policy for pre-100 tools releases. Not sure what the best way of clarifying this in the docs would be.

Engineering Description

Issue:

From the linked support request, it appears there is an incompatibility between mongodump version 4.2 and MongoDB 3.4.22.

The error as reported by the customer is:

The mongodb dump for collection deviceOperation on cluster <CLUSTER_NAME> is failing with the following error.
==========
Failed: error creating intents to dump: error counting <CLUSTER_NAME>.deviceOperation: connection
==========

The command which triggered this error was:

mongodump --uri "mongodb://<User>:<Password>@<NAMES_OF_ALL_NODES>/<DATABASE_NAME>?ssl=true&replicaSet=<CLUSTER_NAME>&authSource=admin" --out <FILENAME. --collection <COLLECTION_NAME>

Workaround:

Use version 4.0.x of the mongodump.

  • Please verify if this is a bug, or a known incompatibility.
  • Please review the other tools in the 4.2 release to determine if there are other incompatibilities/bugs with supported previous versions of MongoDB.
  • If this is a known incompatibility, or a fix is not planned, please open a documentation ticket to update our customer-facing documentation with the information.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 08:08:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.