Hi bbvan,
Apologies for the late reply. As I said earlier we have found the issue regarding wrong results in secondary index query. It will be fixed in future release. Thanks again for bringing this to our notice.
Till then you can apply some tricks to avoid getting into such situation.
- Do not keep the window between deleting and inserting a same primary key very small.
For example -
User deleted a record with key- ‘Car’’ bin - ‘Ford’
User inserted a record with key - ‘Car’ bin - ‘Toyota’
I understand if it is hard to do that. This is very application specific.
- You can increase the gc speed of the secondary index.
asinfo -v “set-config:context=namespace;id=<namespace_name>;indexname=<index_name>;gc-period=0”
asinfo -v “set-config:context=namespace;id=<namespace_name>;indexname=<index_name>;gc-max-units=10000”
Do this for all sindexes in the namespace.
This will speed up the rate at which sindex-gc cleans stale entries.
Can you try this and see if it helps ?
Thanks