When elasticsearch index was read-only once, I cannot restart Optimize anymore and dont know which index I need to activate again

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.3.0
    • Affects Version/s: 2.2.0
    • Component/s: backend
    • None

      When I run out of disk space, ElasticSearch automatically sets index to read-only.
      When I increase the diskspace and restart optimize, elasticsearch starts up, but Optimize still cannot create the MetadataBean on Startup, because it seems like the indexes are still read-only.

      I don't know which index needs to be activated again, I tried the metadata via rest api but this did not help.
      I could imagine that more people will run into this issue.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Felix Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: