Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-3712

2.0 primary "couldn't update slave _ no entry" when secondary 1.8.3

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Trivial - P5 Trivial - P5
    • 2.0.0-rc1
    • Affects Version/s: 2.0.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • ALL

      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

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            tonyh Tony Hannan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: