Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2484

A large number of requests causes Optimize to throw warnings

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.0, 2.6.0-alpha2
    • Component/s: backend
    • Labels:

      Description

      • when:
        • I have a lot of requests against Optimize that need to perform scrolling (e.g. a lot of users loading reports/dashboards)
      • then:
        • Optimize throws a warning after a while:
          10:08:03.200 [I/O dispatcher 2] WARN org.elasticsearch.client.RestClient - request [POST http://localhost:9200/optimize-process-definition/process-definition/_search?typed_keys=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&scroll=60000ms&search_type=query_then_fetch&batched_reduce_size=512] returned 1 warnings: [299 Elasticsearch-6.6.2-3bd3e59 "Trying to create more than 500 scroll contexts will not be allowed in the next major version by default. You can change the [search.max_open_scroll_context] setting to use a greater default value or lower the number of scrolls that you need to run in parallel." "Mon, 22 Jul 2019 07:08:03 GMT"]
          
      • expected:
        • Optimize can handle a large load of requests without any problems

      Hint:
      We should think about to descreasing the scroll timeout value of Elasticsearch or cleaning up the scrolling ourself by closing the scroll after the scrolling is done.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            johannes.heinemann Johannes Heinemann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: