Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6086

Replica active during Warming

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      At least with Solr 4.6.1, replica are considered as active during the warming process.

      This means that if you restart a replica or create a new one, queries will
      be send to this replica and the query will hang until the end of the warming
      process (If cold searchers are not used).

      You cannot add or restart a node silently anymore.

      I think that the fact that the replica is active is not a bad thing.
      But, the HttpShardHandler and the CloudSolrServer class should take the warming process in account.

      Currently, I have developped a new very simple component which check that a searcher is registered.
      I am also developping custom HttpShardHandler and CloudSolrServer classes which will check the warming process in addition to the ACTIVE status in the cluster state.

      This seems to be more a workaround than a solution but that's all I can do in this version.

      Attachments

        1. SOLR-6086.patch
          21 kB
          Ludovic Boutros
        2. SOLR-6086.patch
          29 kB
          Ludovic Boutros
        3. SOLR-6086-temp.patch
          3 kB
          Timothy Potter
        4. SOLR-6086.patch
          21 kB
          Shalin Shekhar Mangar
        5. SOLR-6086.patch
          25 kB
          Shalin Shekhar Mangar

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            shalin Shalin Shekhar Mangar
            lboutros Ludovic Boutros
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 72h
                72h
                Remaining:
                Remaining Estimate - 72h
                72h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment