tree a5e851e3b69241094c13ee1287e59c9e595a3269
parent c4c8f66dcb8c2c04578924a5de16aa7a005b5745
author Luca Milanesio <luca.milanesio@gmail.com> 1580861935 +0000
committer Luca Milanesio <luca.milanesio@gmail.com> 1580935856 +0000

Index account asynchronously and flush upon replication

Account reindexing on remote nodes should not happen immediately
but must queue for asynchronous execution once replication is completed.

Triggering the reindex of the account *before* it arrives on the
All-Users repo would generate two issues:

1. The account would be reindexed with stale data and, when the new
   data will arrive, it won't be reindexed again: we do need to wait
   for the data to arrive through replication.

2. The account index would also populate the cache with stale data
   and even when the new data will arrive the in-memory data would need
   to wait the cache TTL before being visible to the end-user.

NOTE: there is not yet a reliable way to understand *when* the target
      received the new account data. That is the reason why it is
      necessary to wait for *ALL* the nodes to have completed
      replication and then process the account reindexing.

Bug: Issue 12278
Change-Id: Ie442b03f36c1238f6b977e7f5456beff078c9657