Announcement

Collapse
No announcement yet.

Queue messages - DB

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Queue messages - DB

    Hello,

    i have a question regarding the DB increasing size.
    DB that i use is postgres and my question is:
    If i have 300k queued messages in one Mirth channel, did this increase, like a lot, the DB rows/DISK space?
    I have a mirth engine that process a lot of messages per day, is there some routines or some maintenance jobs that we can perform in order to the disk space not increase or just to maintain.

    Thank you
    Best Regards,
    Alex Neiva

  • #2
    Depending on how you have your environment configured, having 300K queued messages can increase the DB size.

    Search the forum for Data Pruner and Message Pruning
    Best,

    Kirby

    Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

    Appliance Version 3.11.4
    Mirth Connect Version 3.8.0
    Java Version 1.6.0_45-b06
    Java (64 bit) Version 1.6.0_45-b06
    Java 7 (64 bit) Version 1.7.0_151-b15
    Java 8 (64 bit) Version 1.8.0_181-b13
    PostgreSQL Version 9.6.8

    Comment


    • #3
      Thanks for the reply.
      Regarding the Data Pruner i have it running every day!
      I don't know for sure if it is correct apply those settings in the pruner option.
      Even if data pruner runs every day, did it delete the pruner rows or just mark them as deleted? Did i need to run the vaccum tool from postgres engine?

      Best Regards
      Best Regards,
      Alex Neiva

      Comment


      • #4
        What do you set "Message Pruning" too in your channels?
        Best,

        Kirby

        Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

        Appliance Version 3.11.4
        Mirth Connect Version 3.8.0
        Java Version 1.6.0_45-b06
        Java (64 bit) Version 1.6.0_45-b06
        Java 7 (64 bit) Version 1.7.0_151-b15
        Java 8 (64 bit) Version 1.8.0_181-b13
        PostgreSQL Version 9.6.8

        Comment


        • #5
          The Data Pruner Settings are:

          Schedule: Daily
          Block Size: 1000
          Prune Events: Yes
          Prune Event Age: 90 days

          Any suggestion?

          Thanks
          Best Regards,
          Alex Neiva

          Comment


          • #6
            In your channels, on the Summary tab, what do you have configured for Message Pruning.
            Best,

            Kirby

            Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

            Appliance Version 3.11.4
            Mirth Connect Version 3.8.0
            Java Version 1.6.0_45-b06
            Java (64 bit) Version 1.6.0_45-b06
            Java 7 (64 bit) Version 1.7.0_151-b15
            Java 8 (64 bit) Version 1.8.0_181-b13
            PostgreSQL Version 9.6.8

            Comment


            • #7
              Ah sorry...

              Metadata:
              Prune metadata older than 365 days

              Content:
              Prune when message metadata is removed
              Best Regards,
              Alex Neiva

              Comment


              • #8
                How long have your channels been processing messages?
                Best,

                Kirby

                Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

                Appliance Version 3.11.4
                Mirth Connect Version 3.8.0
                Java Version 1.6.0_45-b06
                Java (64 bit) Version 1.6.0_45-b06
                Java 7 (64 bit) Version 1.7.0_151-b15
                Java 8 (64 bit) Version 1.8.0_181-b13
                PostgreSQL Version 9.6.8

                Comment


                • #9
                  6 Month
                  Best Regards,
                  Alex Neiva

                  Comment


                  • #10


                    If you have Message Pruning set to 365 days, and the channel has been running for 6 months, the db will continue to grow for another 6 months. Once you go past the 365 day setting that you established, the db should stop growing.

                    If you don't need to keep the messages in Mirth for 365 days, you can adjust your Message Pruning down. You can archive the messages at part of the pruning process.

                    Its dependent on your needs, but usually 2 weeks to a month is the max I keep in Mirth. Everything else is archived.
                    Best,

                    Kirby

                    Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

                    Appliance Version 3.11.4
                    Mirth Connect Version 3.8.0
                    Java Version 1.6.0_45-b06
                    Java (64 bit) Version 1.6.0_45-b06
                    Java 7 (64 bit) Version 1.7.0_151-b15
                    Java 8 (64 bit) Version 1.8.0_181-b13
                    PostgreSQL Version 9.6.8

                    Comment


                    • #11
                      Ok i see... and makes sense!!!
                      But if i archive, i will be able to search in Mirth channel, for some message processed like 8 month ago?
                      Archiving messages have no effect in the DB grow then? it will minimize it?
                      What are the settings in Mirth so i can start archiving messages?

                      Sorry for all the questions. I just need some guidelines on it...
                      Thank you
                      Best Regards,
                      Alex Neiva

                      Comment


                      • #12
                        When you archive messages they are removed from Mirth and will not be available for searching in Mirth.

                        Two pieces to pruning
                        1. Message Pruning configuration within each channel
                        2. Setting --> Data Pruner. This controls how often the pruning process runs, whether messages are just deleted or archived to a folder, etc.
                        Best,

                        Kirby

                        Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

                        Appliance Version 3.11.4
                        Mirth Connect Version 3.8.0
                        Java Version 1.6.0_45-b06
                        Java (64 bit) Version 1.6.0_45-b06
                        Java 7 (64 bit) Version 1.7.0_151-b15
                        Java 8 (64 bit) Version 1.8.0_181-b13
                        PostgreSQL Version 9.6.8

                        Comment


                        • #13
                          So, if i archive messages they will get removed from Mirth, meaning they not occupy space in the DB, and messages are like exported to a folder is that it?
                          To archive messages do i need to check the "allow message archive" in the channel summary?
                          Best Regards,
                          Alex Neiva

                          Comment


                          • #14
                            Yes to both,

                            I believe allow message archiving is checked by default.
                            Best,

                            Kirby

                            Mirth Certified|Epic Bridges Certified|Cloverleaf Level 2 Certified

                            Appliance Version 3.11.4
                            Mirth Connect Version 3.8.0
                            Java Version 1.6.0_45-b06
                            Java (64 bit) Version 1.6.0_45-b06
                            Java 7 (64 bit) Version 1.7.0_151-b15
                            Java 8 (64 bit) Version 1.8.0_181-b13
                            PostgreSQL Version 9.6.8

                            Comment


                            • #15
                              Last questions...
                              Data pruner deletes messages from database correct? Does not just mark them as deleted...
                              Is there some problem if i use Vaccum tool in postgres to shrink the Mirth DB?
                              Best Regards,
                              Alex Neiva

                              Comment

                              Working...
                              X