[SERVER-3712] 2.0 primary "couldn't update slave _ no entry" when secondary 1.8.3 Created: 29/Aug/11  Updated: 11/Jul/16  Resolved: 30/Aug/11

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.0-rc0
Fix Version/s: 2.0.0-rc1

Type: Bug Priority: Trivial - P5
Reporter: Tony Hannan Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

Set up 2 member replica set + arbiter, where primary is running 2.0 and secondary and arbiter are running 1.8.3.
Insert records into primary repeatedly (one every 100ms)

Problem: primary logs following every second
Mon Aug 29 15:55:35 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry
Mon Aug 29 15:55:37 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry
Mon Aug 29 15:55:38 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry
Mon Aug 29 15:55:40 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry
Mon Aug 29 15:55:41 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry
Mon Aug 29 15:55:43 [conn18] couldn't update slave 4e5be9e39eebf4bd3e7b6a93 no entry



 Comments   
Comment by auto [ 30/Aug/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: change log to warning SERVER-3712
Branch: master
https://github.com/mongodb/mongo/commit/6b61f6a212899ebfa21e1ca49d9954fce797bc80

Comment by Eliot Horowitz (Inactive) [ 30/Aug/11 ]

Can you just change it to warning()
Other than that don't change.

Comment by Kristina Chodorow (Inactive) [ 29/Aug/11 ]

It's a harmless log message, but I can quiet it down further.

Comment by Eliot Horowitz (Inactive) [ 29/Aug/11 ]

@kristina - anyway we can make a 2.0 master work with 1.8.3 secondaries?

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