locked
what is the function of search contoller RRS feed

  • Question

  • In Fast ESP we see  search controller  at port 15900  of search engine. these are responsible for which functionality?

    Harvail

    Wednesday, March 28, 2012 1:21 PM

Answers

  • Hello Harvail,

    Fast Search requires name resolution to function properly.  If the components are unable to register with configserver or nameservice then communication failure will occur with unexpected results. 

    If the host is not listed it is possible that the search row would be unavailable/possible search outage.  Or updates to the index would not make it to the system.

    Have you addressed your network/name services issue? 

    Best Wishes,

    Michael Puangco | Senior Support Escalation Engineer | US Customer Service & Support

    Customer Service & Support                        Microsoft| Services

    Tuesday, April 24, 2012 4:48 PM

All replies

  • Hi Harvail,

    Port 15900 is the indexer listener port, and you can check the status at the URL: http://nodename:15900/status.  This will show you the number of indexed documents,
    your indexer partition information, indexer status, total document size, and more.  Let us know if you have more questions.

    Thanks!
    Rob Vazzana

    • Proposed as answer by Rob Va - MSFT Friday, March 30, 2012 8:21 PM
    Thursday, March 29, 2012 9:31 PM
  • Thanks Rob for response. I saw status on 15900 from where this question arises.

    In my installation,on some nodes can see search controller registered and in some these were not registered(due to some name service issues etc).

    So my question was what this search controllers do, if there is no search contoller registered on this page then what will happen(search still works and indexer is still indexing as shown by status)? and which service/Process is reponsible for search contollers?


    Harvail

    Sunday, April 1, 2012 9:32 PM
  • Hello Harvail,

    Fast Search requires name resolution to function properly.  If the components are unable to register with configserver or nameservice then communication failure will occur with unexpected results. 

    If the host is not listed it is possible that the search row would be unavailable/possible search outage.  Or updates to the index would not make it to the system.

    Have you addressed your network/name services issue? 

    Best Wishes,

    Michael Puangco | Senior Support Escalation Engineer | US Customer Service & Support

    Customer Service & Support                        Microsoft| Services

    Tuesday, April 24, 2012 4:48 PM