none
The search request was unable to connect to the search service when the admin mode is down in Multinode configuration RRS feed

  • Question

  • Hi All,

    We have 2 FAST Search Servers and designed as 2 row one column for fault tolerance. (let's say FASTA, FASTB)

    The FASTA is also the admin node.

     <host name="FASTA">
        <admin /> 
    <document-processor processes="12"/>
    <content-distributor id="0" />
    <indexing-dispatcher />
    <crawler role="single" />
    <!--Max targets is the number of CPU's the web analyzer utilizes -->
    <webanalyzer server="true" max-targets="2" link-processing="true" lookup-db="true" redundant-lookup="true" />
        <searchengine row="0" column="0" />
    <query />
      </host>
      <host name="FASTB">
    <document-processor processes="12"/>
    <content-distributor id="1" />
    <indexing-dispatcher />
    <!--This extra instance of the webanalyzer gives extra processing capability -->
    <webanalyzer server="false" link-processing="true" lookup-db="true" />
        <searchengine row="1" column="0" />
        <query />
      </host>
      <searchcluster>
        <row id="0" index="primary" search="true" /> 
        <row id="1" index="secondary" search="true" /> 
      </searchcluster>

    We indexed some documents and search which work perfectly.

    But, when I stopped the FAST Search service on FASTA. I could not search on the FAST Search Center anymore.

    And it is returned as "The search request was unable to connect to the search service".

    IMO, it should propagate search request to another query processing server which is FASTB, right?

    So it is should be searchable... Am I understand correctly?

    Best Regards,

    Andy

    Tuesday, May 22, 2012 5:26 AM

All replies

  • Hi,

    Sorry to bother.

    I just found out that the problem because of I did not register the sharepoint cert into the non-admin node.

    Best Regards,

    Andy

    Tuesday, May 22, 2012 7:04 AM