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

Re-instate the usage of the number of shards in that were accidentaly removed from the codebase

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.12.0-alpha1
    • None
    • None
    • S

      It seems that the setting $.es.settings.number_of_shards is not being used at all in the codebase. This was due to an unintended change in OPT-7348. So we have to re-add the usage to the code base

       

      Testing notes

      Changing the number of shards in the config ($.es.settings.number_of_shards) should be reflected to the database. 

      NOTE: this property only applies the first time Optimize is started and the schema/mapping is deployed on Elasticsearch. If you want to take this property to take effect again, you need to delete all indexes (with it all data) and restart Optimize. This configuration will also only be applied to the current write instance indices. Archive indices will have a single shard regardless

        This is the controller panel for Smart Panels app

          1. image-2023-10-20-09-52-24-375.png
            584 kB
            Giuliano Rodrigues Lima

              Unassigned Unassigned
              giuliano.rodrigues-lima Giuliano Rodrigues Lima
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: