# Scan timeout during read

**URL:** <https://discuss.aerospike.com/t/scan-timeout-during-read/2448>\
**Category:** Hadoop\
**Tags:** scan, hadoop\
**Created:** [January 31, 2016, 1:35am UTC](https://discuss.aerospike.com/t/scan-timeout-during-read/2448 "2016-01-31T01:35:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tivvit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/tivvit/32/314_2.png) [@tivvit](https://discuss.aerospike.com/u/tivvit)\
**Post date:** [January 31, 2016, 1:35am UTC](https://discuss.aerospike.com/t/scan-timeout-during-read/2448/1 "2016-01-31T01:35:37Z")

</div>

Hello, I think I get only some results as input for my hadoop job based on the log below. I there any way how to wait for the scan longer or am I missing something else?

```
2016-01-31 02:03:47,073 INFO [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: queue empty: waiting...
2016-01-31 02:03:48,074 INFO [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: queue empty: waiting...
2016-01-31 02:03:49,074 INFO [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: queue empty: waiting...
2016-01-31 02:03:50,074 INFO [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: queue empty: waiting...
2016-01-31 02:03:51,075 INFO [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: queue empty: waiting...
2016-01-31 02:03:52,075 ERROR [main] com.aerospike.hadoop.mapreduce.AerospikeRecordReader: SCAN TIMEOUT
2016-01-31 02:03:52,080 INFO [main] org.apache.hadoop.mapred.MapTask: Starting flush of map output

```

---

<div class="post-metadata">

**Author:** ![tivvit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/tivvit/32/314_2.png) [@tivvit](https://discuss.aerospike.com/u/tivvit)\
**Post date:** [February 12, 2016, 11:40pm UTC](https://discuss.aerospike.com/t/scan-timeout-during-read/2448/2 "2016-02-12T23:40:44Z")

</div>

I discovered where was the problem. My code threw unhandled exception and the job stuck. So it was my fault, hadoop client is working nicely.
