cancel
Showing results for 
Search instead for 
Did you mean: 

Search service is calling transaction API 100 times per second

cajova_houba
Champ on-the-rise
Champ on-the-rise

Hello,

we're running Alfresco Content Services Community 7.3 and Alfresco Search Services 2.0.5.1, each on its own separate server. Lately, we've noticed quite a high traffic between these two and it turns out the search service keeps calling the following endpoints:

  • /alfresco/service/api/solr/nextTransaction
  • /alfresco/service/api/solr/trasactions

Each endpoint is called about 50 times per second. I've tried to make some sense out of this. Using the search service report API I was able to get the timestamp of the last successful transaction - 20.9. 2024. I then used a SW for capturing packets and found out the search services is trying to fetch new transactions for hourly intervals from 20.9.2024 until the most current date. Again and again. The repository node always responds with the last transaction time being "20.9. 2024".

The only possibly related configuration I found is the alfresco.cron property, which is currently set to 0/10 * * * * ? * meaning the search services should poll Alfresco for new changes every 10 seconds.

I'm not quite sure on how to approach this nor where the problem is. The only Does anyone get any idea where I should look or what the problem might be?

 

Thanks

0 REPLIES 0