Optimize does not start if I configure different ports

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Won't Do
    • Priority: L2 - Critical
    • 2.2.0-alpha1, 2.2.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      • given:
        • I configured a different elasticsearch or optimize port/host than the default one
      • when:
        • I execute the Optimize startup script
      • then:
        • Optimize/elasticsearch are immediately terminated after startup
      • expected:
        • Optimizeand and Elasticsearch run flawlessly under the configured ports/hosts

      Hint:

      • The startup scripts need to parse the configuration file to extract that information
      • You should remove the hints of OPT-1167 in the documentation when this is implemented

            Assignee:
            Unassigned
            Reporter:
            Johannes
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: