How can I increase map_reduce socket timeout?

[Daniel Doubrovkine]

I am seeing a socket timeout from a map_reduce. Any suggestions of how to deal with this?

Thx

dB.

Stack:

Timed out waiting on socket read. /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/networking.rb:325:in `rescue in receive_message_on_socket' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/networking.rb:312:in `receive_message_on_socket' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/networking.rb:184:in `receive_header' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/networking.rb:171:in `receive' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/networking.rb:135:in `receive_message' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/cursor.rb:469:in `block in send_initial_query' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/util/logging.rb:28:in `instrument' /usr/local/lib/ruby/gems/1.9.1/gems/rpm_contrib-2.1.8/lib/rpm_contrib/instrumentation/mongo.rb:26:in `block in instrument_with_newrelic_trace' /usr/local/lib/ruby/gems/1.9.1/gems/newrelic_rpm-3.3.3/lib/new_relic/agent/method_tracer.rb:242:in `trace_execution_scoped' /usr/local/lib/ruby/gems/1.9.1/gems/rpm_contrib-2.1.8/lib/rpm_contrib/instrumentation/mongo.rb:24:in `instrument_with_newrelic_trace' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/cursor.rb:467:in `send_initial_query' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/cursor.rb:458:in `refresh' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/cursor.rb:128:in `next' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/db.rb:505:in `command' /usr/local/lib/ruby/gems/1.9.1/gems/mongo-1.5.2/lib/mongo/collection.rb:619:in `map_reduce' /usr/local/lib/ruby/gems/1.9.1/gems/mongoid-2.4.8/lib/mongoid/collections/master.rb:25:in `block in map_reduce' /usr/local/lib/ruby/gems/1.9.1/gems/mongoid-2.4.8/lib/mongoid/collections/retry.rb:29:in `retry_on_connection_failure' /usr/local/lib/ruby/gems/1.9.1/gems/mongoid-2.4.8/lib/mongoid/collections/master.rb:24:in `map_reduce' /usr/local/lib/ruby/gems/1.9.1/gems/mongoid-2.4.8/lib/mongoid/collection.rb:113:in `map_reduce' /usr/local/lib/ruby/gems/1.9.1/gems/newrelic_rpm-3.3.3/lib/new_relic/agent/method_tracer.rb:491:in `block in map_reduce_with_trace_ActiveRecord_klass_map_reduce' /usr/local/lib/ruby/gems/1.9.1/gems/newrelic_rpm-3.3.3/lib/new_relic/agent/method_tracer.rb:242:in `trace_execution_scoped' /usr/local/lib/ruby/gems/1.9.1/gems/newrelic_rpm-3.3.3/lib/new_relic/agent/method_tracer.rb:486:in `map_reduce_with_trace_ActiveRecord_klass_map_reduce' 

--

dB. | Moscow - Geneva - Seattle - New York
dblock.org - @dblockdotorg

[Durran Jordan]

You're going to have to up the connection timeout on everything, you cannot do it on a per-operation basis for a map/reduce. (Use connect_timeout option in mongoid.yml)

2012/5/7 Daniel Doubrovkine <dbl...@dblock.org>