-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 1.8.2
-
Component/s: None
-
None
It looks like we are sending OP_KILL_CURSORS to the wrong members under certain scenarios.
Reproducible with this code:
#!/usr/bin/env ruby require 'mongo' include Mongo @secondary= MongoClient.new('localhost', 6000, {:slave_ok => true}) @client= MongoReplicaSetClient.new([ 'localhost:3000', 'localhost:6000' ]) @coll= @client['test']['cursor'] @coll.drop 3.times { @coll.insert({:a => 1}) } puts "BEFORE: #{@secondary.db.command({:cursorInfo => 1})}" 100.times do @coll.find({}, {:limit => 2, :read => :secondary}).to_a end puts "AFTER: #{@secondary.db.command({:cursorInfo => 1})}"
- is related to
-
RUBY-505 GETMORE is sent to wrong server if an intervening query unpins the connection
- Closed