User aborted scans can't killed?

I am using java client to execute scans, when the jvm crashed abnormally, I can only kill the scan by aql->"kill_scan ". But as a matter of fact, the job is still there and shown “active(user aborted)”.

Since the previous scan job is still active, other scans is waiting, and no scancallback is invoked.

I tried 3.6.4, and, none of the above versions works in such case.

1 Like

me too meet this issue

This has been resolved since “(Scan) Set scan’s socket send() timeout to be 10 seconds, to accommodate slow or improperly disconnected client.”.

And was further refined with 3.12.1: “(Scan) Write idle-time-out now configurable from client.”

© 2015 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.