You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we see that if a processing creates transactions in a continuous and frequent way, this has side effect to prevent Solr from updating these indexes continuously.
In fact, after investigation, we see that the MetadataTracker is executed every 10s (default cron) but exit without indexing documents related to the transactions it has found. These transactions will be indexed when the traffic will "decrease" on next iterations
After research, this is due to this line of code.
We can see that if a transaction has a date greater than the date at getTimeToStopIndexing(), then it exits without indexing any transactions that might be.
Why not simply remove these transactions from the list in order to keep those that can be indexed and let executing the tracker indexation process ?
Regards,
Thibaut
The text was updated successfully, but these errors were encountered:
Hi,
we see that if a processing creates transactions in a continuous and frequent way, this has side effect to prevent Solr from updating these indexes continuously.
In fact, after investigation, we see that the MetadataTracker is executed every 10s (default cron) but exit without indexing documents related to the transactions it has found. These transactions will be indexed when the traffic will "decrease" on next iterations
After research, this is due to this line of code.
We can see that if a transaction has a date greater than the date at getTimeToStopIndexing(), then it exits without indexing any transactions that might be.
Why not simply remove these transactions from the list in order to keep those that can be indexed and let executing the tracker indexation process ?
Regards,
Thibaut
The text was updated successfully, but these errors were encountered: