Solr
  1. Solr
  2. SOLR-6499

Log warning about multiple update request handlers

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.10
    • Fix Version/s: 5.0, 6.0
    • Component/s: None
    • Labels:
      None

      Description

      Solr 4.10.0 logs the following warning upon startup:

      WARN  - 2014-09-09 17:49:11.455; org.apache.solr.core.RequestHandlers; Multiple requestHandler registered to the same name: /update ignoring: org.apache.solr.handler.UpdateRequestHandler
      

      I've just started the Solr example with bin/solr start to get this warning in example/logs/solr.log

      I don't know if this indicates a real problem but it seems everything works fine despite the warning.

        Activity

        Hide
        Hoss Man added a comment -

        This is because the "/update" handler was made implicit SOLR-6302 (so even if it's not in your solrconfig.xml, it will be created) but was also left in the example solrconfig.xml (for the reasons noted in the SOLR-6302 comments.


        In general the problem is that since we now have implicit request handlers, we need to update the existing logic in RequestHandlers.java that checks for redundant handler definitions to be smart enough to know the difference between two handlers defined in solrconfig.xml with the same name, and a handler defined in solrconfig.xml which is intended to override an implicit handler.

        Show
        Hoss Man added a comment - This is because the "/update" handler was made implicit SOLR-6302 (so even if it's not in your solrconfig.xml, it will be created) but was also left in the example solrconfig.xml (for the reasons noted in the SOLR-6302 comments. In general the problem is that since we now have implicit request handlers, we need to update the existing logic in RequestHandlers.java that checks for redundant handler definitions to be smart enough to know the difference between two handlers defined in solrconfig.xml with the same name, and a handler defined in solrconfig.xml which is intended to override an implicit handler.
        Hide
        Hoss Man added a comment -

        noble: can you follow up with this?

        Show
        Hoss Man added a comment - noble: can you follow up with this?
        Hide
        Noble Paul added a comment -

        I shall fix this right away

        Show
        Noble Paul added a comment - I shall fix this right away
        Hide
        ASF subversion and git services added a comment -

        Commit 1624181 from Noble Paul in branch 'dev/trunk'
        [ https://svn.apache.org/r1624181 ]

        SOLR-6499

        Show
        ASF subversion and git services added a comment - Commit 1624181 from Noble Paul in branch 'dev/trunk' [ https://svn.apache.org/r1624181 ] SOLR-6499
        Hide
        ASF subversion and git services added a comment -

        Commit 1624182 from Noble Paul in branch 'dev/trunk'
        [ https://svn.apache.org/r1624182 ]

        SOLR-6499

        Show
        ASF subversion and git services added a comment - Commit 1624182 from Noble Paul in branch 'dev/trunk' [ https://svn.apache.org/r1624182 ] SOLR-6499
        Hide
        ASF subversion and git services added a comment -

        Commit 1624183 from Noble Paul in branch 'dev/branches/branch_4x'
        [ https://svn.apache.org/r1624183 ]

        SOLR-6499

        Show
        ASF subversion and git services added a comment - Commit 1624183 from Noble Paul in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1624183 ] SOLR-6499
        Hide
        Shawn Heisey added a comment -

        This is a problem in the 4.10.x releases, something that got overlooked because of the timing on the branch_4x commit. We should backport this to the 4_10 branch so that any future 4.x releases will have the fix.

        If a user is trying to override the implicit /update handler in 4.10.x versions with different config options, they will either need to apply this patch or see if there's a workaround. For users wanting to change the update chain, they may be able to simply use default="true" when defining the new chain.

        Show
        Shawn Heisey added a comment - This is a problem in the 4.10.x releases, something that got overlooked because of the timing on the branch_4x commit. We should backport this to the 4_10 branch so that any future 4.x releases will have the fix. If a user is trying to override the implicit /update handler in 4.10.x versions with different config options, they will either need to apply this patch or see if there's a workaround. For users wanting to change the update chain, they may be able to simply use default="true" when defining the new chain.
        Hide
        Anshum Gupta added a comment -

        Bulk close after 5.0 release.

        Show
        Anshum Gupta added a comment - Bulk close after 5.0 release.

          People

          • Assignee:
            Noble Paul
            Reporter:
            Andreas Hubold
          • Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development