Thanks for the reply. Glad to know that changing connected indexer is a normal behavior, so it's easy to troubleshoot this issue. We tried other file price.csv.zip and run the search * source="/data/price.csv.zip". IT WORKS. Therefore we think it is the issue about the file.
Actually, when we create the indexers in the cluster, we clone a previous distrubuted index where we had forwarded the tutorialdata.zip. Although we remove all the database on the new indexer, will it save the hash or something else to mark the file forwarded? When we forward tutuorialdata.zip again, the indexer will ignore it by checking the hash？
If it is, how can we clean the hash records to make the new indexer working for a duplicate file?
Thank you very much.
... View more
It is correct that you do not need to set up the deployer connectivity until the first time that you need to use the deployer.
However, the deployer is the only supported method for deploying apps and other configurations to cluster members. So, sooner or later, you will need to set up the deployer. You cannot deploy an app until you do so.
For this reason, we recommend that you configure the deployer and connectivity to the deployer at the same time that you initially configure the cluster itself. There is usually no reason to wait until later.
... View more