Query timeout after restart server


#1

After restart the server, aql show one record.

aql> show sets
+-----------+----------------+----------------------+---------+------------------------------+------------+---------------------+
| n_objects | set-enable-xdr | set-stop-write-count | ns_name | set_name | set-delete | set-evict-hwm-count |
+-----------+----------------+----------------------+---------+------------------------------+------------+---------------------+
| 13188778  | "use-default"  | 0                    | "test"  | "T1"              | "false"    | 0                   |
| 40801348  | "use-default"  | 0                    | "test"  | "T2”    | "false"    | 0                   |
| 41400366  | "use-default"  | 0                    | "test"  | "T3”  | "false"    | 0                   |
| 6270495   | "use-default"  | 0                    | "test"  | "T4”         | "false"    | 0                   |
| 6507591   | "use-default"  | 0                    | "test"  | "T5” | "false"    | 0                   |
| 1         | "use-default"  | 0                    | "test"  | “T6”            | "false"    | 0                   |
| 1         | "use-default"  | 0                    | "test"  | “T7”             | "false"    | 0                   |
+-----------+----------------+----------------------+---------+------------------------------+------------+---------------------+
7 rows in set (0.001 secs)

But when try to query the table, AeroSpike timeout.

aql> select * from test.T6
Error: (9) Client timeout: timeout=1000 iterations=1 failedNodes=0 failedConns=0

This happens after the server machine reboot.


#2

Hi James, Querying a table in aerospike uses scan internally. Scan goes through each partition and returns data from that if exists with filtering based on set name. There are 4096 partition to scan. So even if 1 record is there in a set, it will scan each portion. Because of that you are seeing timeout.

You can increase the timeout interval by running following:

aql> set timeout 10000