[SERVER-7714] currentop() from master in master-slave pair includes invalid BSON Created: 19/Nov/12  Updated: 11/Jul/16  Resolved: 26/Nov/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.3.0
Fix Version/s: 2.3.2

Type: Bug Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Kevin Matulef
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4045 Display queries for getmore ops in db... Closed
Related
is related to SERVER-7562 Change OplogReader to send query as O... Closed
Operating System: ALL
Participants:

 Description   

Same problem as SERVER-7562 but for masters of master-slave pairs, rather than primaries of replica sets. Calling db.currentOp() from PyMongo against the current nightly throws a BSON parse error, if there is currently a slave tailing the master's oplog. See Jenkins failures:

https://jenkins.10gen.com/view/Python/job/mongo-python-driver/



 Comments   
Comment by auto [ 26/Nov/12 ]

Author:

{u'date': u'2012-11-26T17:59:55Z', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}

Message: SERVER-7714 use appendTimestamp, don't corrupt currentOp output with master-slave
Branch: master
https://github.com/mongodb/mongo/commit/84b4f2f2325c1e7d2f8d12fff1c3909bf5f06ce0

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