Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
3.2.1
-
None
-
ALL
-
Description
This behavior was introduced in MongoDB shell version 3.2.1
If the first command after connecting with the shell is a read concern query, the shell throws Error: readConcern requires use of read commands.
Subsequent queries complete successfully.
MongoDB shell version: 3.2.1
|
connecting to: test
|
Server has startup warnings:
|
2016-01-22T15:45:26.193-0500 I CONTROL [initandlisten]
|
2016-01-22T15:45:26.193-0500 I CONTROL [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000
|
replset:PRIMARY> db.blah.find({}).readConcern("majority")
|
Error: readConcern requires use of read commands
|
replset:PRIMARY> db.blah.find({}).readConcern("majority")
|
replset:PRIMARY>
|
Attachments
Issue Links
- duplicates
-
SERVER-22440 Shell incorrectly issues first query in legacy read mode
-
- Closed
-