Many "Timed out waiting on socket read" since upgrading to 2.6.7 from 2.4.x

[jamieorc]

Last week I upgraded to 2.6.7 from 2.4.12. I have many nightly processes that run on one server against another server that hosts Mongodb.

Using Ruby.

Since the upgrade, I'm seeing a ton of "Timed out waiting on socket read" errors and my processes are failing to complete.

Is there anything obvious and known to the community that would cause this to appear from a simple upgrade?

I also moved the Ruby driver up from 1.11.x to 1.12.0. 

Cheers,

Jamie

[jamieorc]

I reverted my Ruby driver from 1.12.0 to 1.11.1 and so far the problem has gone away. I'll know more after tonight's processes run. Looks to be a change or problem in the current Ruby driver.

Jamie

[Emily S]

Hi Jamie

Thanks for reporting this. I work on the Ruby driver so I'd like to get some more information to determine if there is a regression from 1.11.x to 1.12.0

Can you tell me please:

What exact patch level of 1.11 you are using?

Are you doing all the same type of operation when you get the timeout error or do you get the error randomly? I.e. a series of reads or writes?

If you could send a stack trace, that'd be great.

Thanks

Emily

[jamieorc]

Emily, sorry I never replied to this. Apparently I neglected to email-subscribe to this thread. I just ran into this problem again after upgrading from 1.11.1 to 1.12.3. I want to upgrade as I'm testing against Mongodb 3.0 and need the 1.12.x to 3.0.x compatibility. 

[jamieorc]

query looks like:

```

bundle exec rails runner 'puts Datapoint.count(:name => /(^env)|(^hum)/, :manually_assessed.ne => true)'

```

I ran it on same code with 1.11.1 driver against same database and got:

```

1155275

```

against the 1.12.3 driver:

```

bundle/ruby/2.1.0/gems/railties-3.2.20/lib/rails/commands/runner.rb:54:in `eval': Timed out waiting on socket read. (Mongo::OperationTimeout)

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/networking.rb:330:in `receive_message_on_socket'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/networking.rb:191:in `receive_header'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/networking.rb:182:in `receive'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/networking.rb:146:in `receive_message'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/cursor.rb:551:in `block in send_initial_query'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/functional/logging.rb:55:in `block in instrument'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/functional/logging.rb:20:in `instrument'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/functional/logging.rb:54:in `instrument'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/cursor.rb:547:in `send_initial_query'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/cursor.rb:532:in `refresh'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/cursor.rb:139:in `next'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/db.rb:605:in `command'

bundle/ruby/2.1.0/gems/mongo-1.12.3/lib/mongo/cursor.rb:216:in `count'

bundle/ruby/2.1.0/gems/plucky-0.6.6/lib/plucky/query.rb:118:in `count'

from (eval):1:in `<top (required)>'

bundle/ruby/2.1.0/gems/railties-3.2.20/lib/rails/commands/runner.rb:54:in `eval'

bundle/ruby/2.1.0/gems/railties-3.2.20/lib/rails/commands/runner.rb:54:in `<top (required)>'

bundle/ruby/2.1.0/gems/railties-3.2.20/lib/rails/commands.rb:64:in `require'

bundle/ruby/2.1.0/gems/railties-3.2.20/lib/rails/commands.rb:64:in `<top (required)>'

script/rails:6:in `require'

script/rails:6:in `<main>'

```

[Jamie Orchard-Hays]

Some more info on this:

Downloaded same data to Mongo 3.0.4 instance on my Macbook Air (i7, 8gig) The query ran fine with the 1.12.3 driver. It did not time out and the process returned the number of docs.

It’s failing on a both staging-specified Ubuntu 14.04 and production-specified Ubuntu 14.04 servers.

Staging: Mongo 2.6.9: got same error both locally and from a remote server.

Production: Mongo 3.0.4: same error locally.

Any help appreciated and will be glad to file a bug report.

Cheers, 

Jamie

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
 
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to a topic in the Google Groups "mongodb-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mongodb-user/gZjBg8k4N8o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/0ec4d3f1-6ca0-4e58-a877-576e198d8387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.