Scan stuck: is it dead or still running?


#1

We have a scan that was aborted but is still showing up in aql and its run_time keeps growing. Trying to kill it again does not work. Is this scan really dead or is it still running? Is there a way to clean it from the list of active scans?

aql> show scans
+---------------------+-------------+-----------+--------------+-----------+-------------+--------------+-----------------+--------------+-----------+----------+------------------+--------+-----------+------------+--------------+-----------+-------------+
| udf-avg-runtime(ms) | ns          | recs_read | udf-filename | run_time  | udf-success | udf-function | trid            | job-progress | set       | priority | job-type         | module | status    | udf-failed | net_io_bytes | mem_usage | udf-updated |
+---------------------+-------------+-----------+--------------+-----------+-------------+--------------+-----------------+--------------+-----------+----------+------------------+--------+-----------+------------+--------------+-----------+-------------+
| 0                   |        "db" | 3036298   | "tools"      | 958813132 | 3036298     | "setTTL"     | 535487994628248 | 5            | "dvusrmp" | 2        | "BACKGROUND_UDF" | "scan" | "ABORTED" | 0          | 30           | 0         | 0           |
+---------------------+-------------+-----------+--------------+-----------+-------------+--------------+-----------------+--------------+-----------+----------+------------------+--------+-----------+------------+--------------+-----------+-------------+
1 row in set (0.000 secs)
OK

aql> q

ubuntu@ip-10-45-54-41:~$ aql
Aerospike Query
Copyright 2013 Aerospike. All rights reserved.

aql> KILL_SCAN 535487994628248
Error: (2) Transaction Not Found

Thanks!


#2

The status is ‘ABORTED’ which is why it’s not found by KILL_SCAN. The information about the most recent scans will be around for a bit, then go away. The Managing Scans article has more detail. In server versions >= 3.6.0 there are a few new scan enhancements.


#3

@rbotzer

It’s been several weeks now and other aborted scans clear right away which is why I thought it’s stuck. Is there anything I can do to clear it? I am on 3.5.15 still.

Thanks!


#4

When you do new scans does the information about the aborted one still linger?

The main thing you can do is move to 3.6.1. The 3.6.0 release added several significant changes to scans.


#5

Correct it does.

Alright - will look into updating.