SPSearchServiceApp: Added logic and parameter to provision default search topology #1401
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Added optional ProvisionDefaultTopology (boolean) parameter to control should the SPSearchServiceApp provision deafult search topology. Use 'ProvisionDefaultTopology = $true' parameter to provision default search topology. When this parameter is defined and value is TRUE then topology is created as below:
First we check are there any servers having Search or ApplicationWithSearch role. If there are then all search components are
provisioned to all these servers
If no Search or ApplicationWithSearch role servers exist then we check are there servers having Custom role. If yes then all
search server components are provisioned to one (1) server having Custom role
If no servers exist having roles defined in 1 and 2 then we check is this SingleServer or SingleServerFarm deployment and if yes the all search server components are provisioned to that single server
If you do not want to provision default topology then you need to define search topology using the SPSearchTopology resource!
This Pull Request (PR) fixes the following issues
None
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).
help.
This change is