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

It would be nice to have a way to insure that config and schema API calls have propagated to all cores

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 6.5, 7.0
    • None
    • None
    • None

    Description

      While working on SOLR-10493 I discovered that the test was failing because a config change had been made. That test goes on to delete collections, but the config change is still sending out reload commands. The sequence is something like this:

      1> config change request is made.
      2> call returns, but various core reload commands are still being sent out
      3> collection is deleted
      4> one of the reloads from <2> arrives

      Test fails because the core (and descriptor) is gone.

      This was succeeding before SOLR-10007 because (I think) there was a copy of the coreDescriptor being held in several places and one of the un-deleted ones was being used.

      It would be good if there were a way to be sure that that config and schema calls had been propagated to all replicas in all affected collections.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              erickerickson Erick Erickson
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: