# Resource temporarily unavailable **URL:** \ **Category:** Ruby Client\ **Created:** [July 25, 2018, 7:58am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383 "2018-07-25T07:58:39Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 25, 2018, 7:58am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/1 "2018-07-25T07:58:39Z")
In my JRuby application, I am getting following error periodically, Aerospike::Exceptions::Connection: Resource temporarily unavailable - errno backtraces disabled; run with -Xerrno.backtrace=true to enable with following configuration (3 nodes), ``` network { service { address any port 3000 } heartbeat { mode mesh address 10.240.0.53 port 3002 # To use unicast-mesh heartbeats, remove the 3 lines above, and see # aerospike_mesh.conf for alternative. mesh-seed-address-port 10.240.0.53 3002 mesh-seed-address-port 10.240.0.34 3002 mesh-seed-address-port 10.240.0.48 3002 interval 150 timeout 10 } fabric { port 3001 } info { port 3003 } } ``` In addition to this, I have also added timeouts for read and write operation(250ms). Is there any particular reason behind this error? XPost: [https://stackoverflow.com/questions/51538049/aerospike-resource-temporarily-unavailable](https://stackoverflow.com/questions/51538049/aerospike-resource-temporarily-unavailable) ---
**Author:** ![Jan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/jan/32/1124_2.png) [@Jan](https://discuss.aerospike.com/u/Jan)\ **Post date:** [July 25, 2018, 8:43am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/2 "2018-07-25T08:43:06Z")
Based on the error message (“Resource temporarily unavailable”) this is probably a form of EAGAIN error where the client is trying to read from or write to a TCP socket asynchronously but fails to do so. Can you please enable backtraces (i.e. `jruby -Xerrno.backtrace=true ...`) so we can see exactly where this exception is happening? What version of the client are you using? What version of JRuby are you using? ---
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 25, 2018, 9:00am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/3 "2018-07-25T09:00:08Z")
Ok. Let me check with `-Xerrno.backtrace=true` option I am using `jruby-9.1.15.0` and aerospike client `2.7.0` ---
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 25, 2018, 9:17am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/4 "2018-07-25T09:17:22Z")
@Jan I am using Community edition of aerospike with 3 nodes. And its operating at around 700 writes/second, 250 reads/second ---
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 26, 2018, 12:20pm UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/6 "2018-07-26T12:20:11Z")
Here is backtrace, ````auto /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/socket/base.rb:44 in read_from_socket /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/socket/base.rb:31 in read /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/command/write_command.rb:47 in parse_result /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/command/command.rb:403 in execute /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/client.rb:857 in execute_command /GEM_ROOT/gems/aerospike-2.7.0/lib/aerospike/client.rb:117 in put``` ```` ---
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 26, 2018, 12:25pm UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/7 "2018-07-26T12:25:19Z")
We are trying to replace Redis with Aerospike. But getting more timeouts than redis. ---
**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\ **Post date:** [July 28, 2018, 2:52am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/8 "2018-07-28T02:52:49Z")
Does this happen all the time? How much load is the server under? Have you checked your bottlenecks (IO/Network/CPU)? Anything in the aerospike log? What does your topology look like - server/client specs, hops between nodes/server\<-\>client? Any latency in the histograms? ---
**Author:** ![Pandurang\_w](https://avatars.discourse-cdn.com/v4/letter/p/85e7bf/32.png) [@Pandurang\_w](https://discuss.aerospike.com/u/Pandurang_w)\ **Post date:** [July 28, 2018, 3:53am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/9 "2018-07-28T03:53:00Z")
Yes It happens like in every 2-3 hours. Looks like known issue [Aerospike::Exceptions::Connection: Errors · Issue #67 · aerospike/aerospike-client-ruby · GitHub](https://github.com/aerospike/aerospike-client-ruby/issues/67) It works very well if don’t put Timeout. ---
**Author:** ![Jan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/jan/32/1124_2.png) [@Jan](https://discuss.aerospike.com/u/Jan)\ **Post date:** [August 7, 2018, 7:19am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/10 "2018-08-07T07:19:03Z")
Please try out Ruby client v2.8.0 that got released to [rubygems.org](https://rubygems.org/gems/aerospike) yesterday. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\ **Post date:** [August 13, 2018, 7:19am UTC](https://discuss.aerospike.com/t/resource-temporarily-unavailable/5383/11 "2018-08-13T07:19:06Z")
This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.