Ansicht von 2 Antwort-Threads
  • Autor
    Beiträge
    • 13. Oktober 2021 um 6:31 Uhr - Views: 884 #12012
      p-sandor
      Teilnehmer

        Hi,

        I have migrated an OTRS system to Otobo Docker with Elasticsearch.

        Currently the database taking up 30+GB of disk space which is fine, this is about the same as the old system. However, Otobo’s Elasticsearch container taking up almost as much.

        Is this normal? Is it possible to compact or clear this?

      • 13. Oktober 2021 um 10:15 Uhr #12017
        Giordano Torre
        Teilnehmer

          Good Morning,

          I have installed Otobo on new server with docker installation.

          I have 30G space on my server.

          Now after 15 days I have 36% disk usage.

          Is it normal??!?!?

          Thank You

           

        • 21. Juni 2023 um 8:08 Uhr #15291
          Lennart G
          Teilnehmer

            Hi,

            this thread is already a few days old, but I have the same problem.

            We are using Otobo with Docker and created about ~150 test tickets. I notice, that the container otobo_elastic_1 grows extreme. I have already extended the disk space and restarted the entire server. After that I had no problems for a few days.

            Yesterday I created about 10 tickets in the system. In the server monitoring I can see that after creating the tickets the available disk space of 15 GB was completely used up.

            It could be a kind of service that stuck in a loop untile it runs out of disk space.

            Any ideas on that?

        • Autor
          Beiträge
        Ansicht von 2 Antwort-Threads
        • Du musst angemeldet sein, um auf dieses Thema antworten zu können.