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

CoreAdminHandler Unload no longer handles null core name.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 4.10, 5.0, 5.1, 5.2
    • 5.3, 6.0
    • clients - java
    • Windows 8 and Windows Server 2012 R2

    Description

      Pre 4.10 If a null core name was passed in it would be handled as a bad request with error message "No such core exists [ null ]". From 4.10 onwards an unload call goes to CoreContainer unload where the first action taken is removing the core from coreInitFailures which throws when given null and instead of returning the expected BadRequest "Cannot unload non-existent core [null]" it returns InternalServerError "java.lang.NullPointerException
      at java.util.concurrent.ConcurrentHashMap.replaceNode(Unknown Source)
      at java.util.concurrent.ConcurrentHashMap.remove(Unknown Source)
      at org.apache.solr.core.CoreContainer.unload(CoreContainer.java:661)..."

      This was found due to mixing up query parameter "name" used in create vs "core" in unload. As a result this is easily reproducible with http://localhost:8983/solr/admin/cores?action=UNLOAD&name=core0

      Attachments

        1. SOLR-7705.patch
          2 kB
          Edward Ribeiro
        2. SOLR-7705.2.patch
          2 kB
          Edward Ribeiro

        Activity

          People

            shalin Shalin Shekhar Mangar
            johncall John Call
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

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