`No alive nodes. All the 1 nodes seem to be down.` in `fulltextsearch:reset` but `fulltextsearch:stop` is working

[cdhermann]

As described in https://github.com/nextcloud/all-in-one/discussions/4481 my Nextcloud logs are flooded with error messages like Retry 0: cURL error 6: Could not resolve host: nextcloud-aio-fulltextsearch (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://elastic:XXX@nextcloud-aio-fulltextsearch:9200/nextcloud-aio/_search?from=0&size=5&_source_excludes=content.

BUT, the search itself works perfectly fine.

I followed the instructions on https://github.com/nextcloud/all-in-one/discussions/2509 to reset the Elasticsearch container. Unfortunately, the command php occ fulltextsearch:reset gives the following error

# sudo docker exec --user www-data -it nextcloud-aio-nextcloud bash
0aed8be8812d:/var/www/html$ php occ fulltextsearch:stop
stopping all running indexes
0aed8be8812d:/var/www/html$ php occ fulltextsearch:reset
WARNING! You are about to reset your indexed documents:
- provider: ALL
- collection: ALL

Do you really want to reset your indexed documents ? (y/N) y

WARNING! This operation is not reversible.
Please confirm this destructive operation by typing 'reset ALL ALL': reset ALL ALL

In SimpleNodePool.php line 77:

  No alive nodes. All the 1 nodes seem to be down.


fulltextsearch:reset [--output [OUTPUT]] [--provider PROVIDER] [--collection COLLECTION]

The search is still working perfectly fine.

• How to make the fulltextsearch app itself believe it is working fine?
• Why is the stop command working if a follow-up reset command doesn't find any alive nodes?