Announcement

Collapse
No announcement yet.

Data Pruner on excessively large channels

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

  • Data Pruner on excessively large channels

    I've been running the data pruner for the first time on one of our servers and it's been running for 68 hours so far, working on a single channel that has 10s of millions of messages (we forgot to turn on the pruner at first).

    Do you think it's actually working, or stuck?

    I'm monitoring the size of the table but it's not shrinking so far.

    SELECT pg_size_pretty( pg_database_size('pier02_mirthdb') );
    Attached Files

  • #2
    I've had issues with this in the past. If you are unable to get the pruner to complete, you can:

    Save the channel externally
    Undeploy and delete the channel
    Import the channel back into Mirth
    Deploy

    NOTE: This deletes ALL of the message history. So if you need recent message history, you are going to want to save that externally also.
    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
      Doing a Remove All Messages on the channel will truncate the tables and have the same effect as deleting and restoring the channel.

      On older mirth versions, without verifying I'm thinking it is prior to 3.5 or 3.6, only postgres did a truncate, and the others database engines deleted all the rows.

      Comment


      • #4
        Good to know Tony!
        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
          Thank you for the response. We ended up simply deleting the channel and re-importing, which worked great.

          Comment

          Working...
          X