I am experiencing an odd behavior when running scans using AerospikeClient.scanNode (java API) to retrieve all records in a set. (Some background that may or may not be relevant: This code is running inside hadoop map-reduce, in which there is one mapper for each node).
There is a long delay (1-3 minutes) before the first record is returned, then a period of 1-3 minutes where records are returned (at a rate of a few thousand per second), then a 1-3 minute delay, then 1-3 minutes of data, and so on.
There are no other jobs running. The cluster appears to be otherwise healthy, responding to a few thousand non-job related requests per second.
Does anyone have any suggestions for what may be causing this, or how to proceed investigating?