Uploaded image for project: 'Planet4'
  1. Planet4
  2. PLANET-5040

#425554: Elastic search is incredibly slow

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Should have Should have
    • None
    • 4
    • Search
    • Sprint #133

      Planet 4 Bug Report
      ===================

      Requestor's email: okeur@greenpeace.org
      Requestor's Skype: oscar.keur

      Page: https://www.greenpeace.org/nl/acties/plastic

      Description of the issue: Since 10th of April around 10AM
      the 'p4-es-elasticsearch-client.default.svc.cluster.local' resource is
      taking more and more time to respond. Looking at New Relic around 80-95% of
      the time on the '/page' endpoint is spent on waiting for ES to respond.
      Since it is always at perfectly 30000ms I guess it's actually timing out?
      Maybe that might (partly?) explain my other bug reports?
      Looking at the response times atm I would say it's getting more and more
      urgent. Taking the Apdex score from New Relic for example; 23% of our users
      are getting slow pages. This is hurting leads generation.

      An stack trace from New Relic as an example
      https://rpm.newrelic.com/accounts/301342/applications/59234590/transactions?type=app#id=5b225765625472616e73616374696f6e2f416374696f6e2f70616765222c22225d&app_trace_id=67efd9d8-89e9-11ea-b750-0242ac11000b_45097_58589&tab-detail_67efd9d8-89e9-11ea-b750-0242ac11000b_45097_58589=trace_details

        1. image-2020-05-06-09-10-10-025.png
          41 kB
          Oscar Keur
        2. Oscar Keur - Elastic Search.png
          285 kB
          Erick Consejo
        3. Screenshot from 2020-05-06 10-35-17.png
          91 kB
          Oscar Keur
        4. Screenshot from 2020-05-06 10-35-41.png
          40 kB
          Oscar Keur
        5. Screenshot from 2020-05-06 10-37-05.png
          82 kB
          Oscar Keur

            pvincent Pieter Vincent
            okeur Oscar Keur
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: