Hello,
I am new in this mailing list, so sorry if this has already been asked or if the question is too stupid :).
Our organization is running a devpi-server and I observed that the indexer that is used for the devpi-web search is only triggered when I restart the server from what I can see in the logs. This is what I can see in the logs when I restart the service:
Feb 01 13:46:36 devpi-server[8644]: 2022-02-01 13:46:36,723 INFO [IDX] Indexer queue size ~ 400
Feb 01 13:46:36 devpi-server[8644]: 2022-02-01 13:46:36,987 INFO [IDX] Committing 5 new documents to search index.
...
Feb 01 13:46:41 devpi-server[8644]: 2022-02-01 13:46:41,577 INFO [IDX] Committing 4 new documents to search index.
Feb 01 13:46:41 devpi-server[8644]: 2022-02-01 13:46:41,831 INFO [IDX] Indexer queue size ~ 392
...
An example of what I'm trying to explain a side effect of this is that my organization has been pushing packages to pypi in https://pypi.org/project/sphinx-bluebrain-theme/#history, but using the search functionality only showed the version 0.2.5 (but if you enter in the package showed in the web interface it tells you a message that there is a new version available and the new 0.2.8 package is also available through the devpi-server, it's just a thing from the search). When I restarted the service, the search started to show 0.2.8.
So I was wondering, is this behaviour expected? Do I need to restart periodically the server to rebuild the search index? Or is there anything that I'm missing from the configuration that would do this for me?
Thanks,
Luis.
