Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-2832

Hibernate Search produces huge stack traces when Elasticsearch request processing threads are interrupted

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.9.0.Beta1
    • Component/s: elasticsearch
    • Labels:
      None

      Description

      After HSEARCH-2764 Closed (and maybe also before, but probably to a lesser extent), when Elasticsearch request processing threads are interrupted, the requests are considered as failed, and their content is printed out as part of the stack trace. It would be acceptable (-ish) if it was only the currently executing request, but it seems pending requests also get printed out, resulting in huge stack traces (we're talking about dozens of megabytes) when under heavy load, for instance when mass indexing.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                yrodiere Yoann Rodière
                Reporter:
                yrodiere Yoann Rodière
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: