Secondary indexes very slow in cold restart

Operations Tuning
,
8

Hi yestpea,

When you reboot aerospike, it issues a namespace scan to populate all the secondary indexes. This scan will do 1 random i/o per record. In your case it is 300M. Ideally it should not take 27 hours to scan the namespace and populate all the secondary indexes. So there is something wrong going on here. We are trying to figure out this. So far, I have failed to reproduce this locally.

From what I understand you have around 6 secondary indexes in 6 different sets, right ?

FYI : You can use following command in aql to know the number of sindexes you have.

aql > show indexes

To move further can you tell us -

  1. What is your average record size ?

  2. What type of data you were indexing (string or integer). If string, what was the average size of the string.