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
Nice job with the Symfony Messenger integration , works well , but I'm having an issue with aliases.
When I'm running the populate job I've got downtime (empty nodes which I didn't had previously , without async) and I'm not really sure what's the approach in avoiding that downtime.
Resetting X
Refreshing X
Resetting Y
Refreshing Y
I know I can use --no-reset to avoid refreshing , but how would I force a refresh considering that the populate is now async ?
Thanks and hopefully I was clear.
The text was updated successfully, but these errors were encountered:
I'm not sure that you can achieve that due to the whole async approach. It first resets the index, then queues all populates via messenger, and then messenger starts consuming.
I'm afraid there is no way to do reset of the index before messenger starts consuming messages and re-populates your index.
One thing that I'm using is passing an --index=<index_name> --pager-persister=async and thus reseting single index, tho I assume you don't want to run manually command for each index, but rather to re-populate all indexes at once.
Hey guys.
Nice job with the Symfony Messenger integration , works well , but I'm having an issue with aliases.
When I'm running the
populate
job I've got downtime (empty nodes which I didn't had previously , without async) and I'm not really sure what's the approach in avoiding that downtime.Resetting X
Refreshing X
Resetting Y
Refreshing Y
I know I can use
--no-reset
to avoid refreshing , but how would I force a refresh considering that the populate is now async ?Thanks and hopefully I was clear.
The text was updated successfully, but these errors were encountered: