FAST Search - Query SSA App pools RRS feed

  • Question

  • Should Query SSA "Search Web Admin Service" and "Search Query and Site Settings Web Service" be in separate IIS App Pools with separate managed service accounts? Why/Why not?

    Also why should/shouldn't FAST Query share app pool with Content SSA?

    Tuesday, August 24, 2010 7:38 AM


  • The general reason stated on TechNet for AppPools is "By creating new application pools and assigning Web sites and applications to them, you can make your server more efficient and reliable, and your other applications always available, even when the applications in the new application pool terminate".

    The reason not to share they query ssa with the content ssa is if you happen to have a crawler which wrecks havoc and takes down the app pool it is running under, you do not want searching to go down as well. Having two app pools ensures that searching will work if indexing dies and vice versa.

    As for the admin and query sharing, that would be due to security. There could potentially be issues with a general query having access to admin. Also there could be the same issue as above, one function might take down the app pool, and you want high availability on the searches.

    So, different accounts have different access levels and will isolate what a particular application running on that AppPool has access to. Having different AppPools for the applications ensures that a troublesome application doesn't interfere with the other applications.

    That said, you are free to experiment and share apps on the same AppPool, and you might not have any issues at all, and security might not be that big of a problem either. And the 10 app pool limit still stands per server, so either scale out, or bundle services together which you are comfortable with on the same AppPool.

    Hope this sheds some light on your question.

    Mikael Svenson 

    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4 -
    Saturday, April 16, 2011 7:19 PM