LBRYCommunity/hub
1
0
Fork 0
Code Issues 35 Pull requests 6 Projects Releases Packages Wiki Activity

prune stale trending notifications during initial bulk sync

Browse source
This commit is contained in:
Jack Robison 2022-06-29 12:17:39 -04:00
parent 903a44d991
commit 2363865e00
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
hub/elastic_sync/service.py
View file

@ -435,6 +435,11 @@ class ElasticSyncService(BlockchainReaderService):
for k, v in self.db.prefix_db.trending_notification.iterate(start=(batch_height,), stop=(batch_height+10000,)):
notifications[k.claim_hash].append(TrendingNotification(k.height, v.previous_amount, v.new_amount))
async for (k,), v in self.db.prefix_db.claim_to_txo.multi_get_async_gen(
self._executor, [(claim_hash,) for claim_hash in notifications]):
if not v:
notifications.pop(k)
for claim_hash, trending in notifications.items():
yield self._update_trending_query(self.index, claim_hash, trending)
self._trending.clear()
@ -452,7 +457,7 @@ class ElasticSyncService(BlockchainReaderService):
else:
success += 1
if cnt % batch_size == 0:
self.log.info(f"indexed {success} claims")
self.log.info(f"indexed {success}/{cnt} claims")
finished = True
await self.sync_client.indices.refresh(self.index)
self.log.info("indexed %i/%i claims", success, cnt)