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

ConcurrentUpdateSolrServer hang in blockUntilFinished.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.5
    • None
    • None

    Description

      Not sure what is causing this, but SOLR-6136 may have taken us a step back here. I see this problem occasionally pop up in ChaosMonkeyNothingIsSafeTest now - test fails because of a thread leak, thread leak is due to a ConcurrentUpdateSolrServer hang in blockUntilFinished. Only started popping up recently.

      Attachments

        1. CPU Sampling.png
          17 kB
          Stephan Lagraulet
        2. SOLR-6406.patch
          16 kB
          Yonik Seeley
        3. SOLR-6406.patch
          2 kB
          Mark Miller
        4. SOLR-6406.patch
          13 kB
          Yonik Seeley

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SOLR-8129 HdfsChaosMonkeyNothingIsSafeTest failures

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SOLR-8203 Stop processing updates more quickly on shutdown

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SOLR-6136 ConcurrentUpdateSolrServer includes a Spin Lock

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              yseeley@gmail.com Yonik Seeley
              markrmiller@gmail.com Mark Miller
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: