I noticed that too. The only way i found to use "native" autospinstaller is to create all components on the server.
AFAIK, the query component wouldn't fonction anyway if the index one is down, so we're talking only performance issues.
I script separately the search topology if a customer wants two serveurs. There is a way to partition, but no way to load balance i saw.
Wish i had more time to investigate :)
- if you dont include query on the search server, the topology doesnt get activated (pending components, which is logical)
-
if you setup a query component on another server, nothing happens (which isnt, it should instanciate component and activate topology)
AFAIK, the query component wouldn't fonction anyway if the index one is down, so we're talking only performance issues.
I script separately the search topology if a customer wants two serveurs. There is a way to partition, but no way to load balance i saw.
Wish i had more time to investigate :)