Shrinking communication_log_object_entry table

Moderator: crythias

Post Reply
vincentb
Znuny newbie
Posts: 12
Joined: 30 Jan 2021, 07:51
Znuny Version: 6 community
Real Name: Vincent B.

Shrinking communication_log_object_entry table

Post by vincentb »

Hello,

I run OTRS 6. The (MariaDB) communication_log_object_entry table is growing and its size is now more than 40GB, which becomes to be a problem. (I think this growth is mainly because there is really a lot of postmaster filters that are applied to the incoming emails, and there are many incoming emails...)

I would like to shrink this communication_log_object_entry table.
Can I just delete the oldest entries (they have a create_time recorded)?
Is there some risk/inconvenience to do that?

Thank you for your insights.
root
Administrator
Posts: 3960
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Shrinking communication_log_object_entry table

Post by root »

Hi,

The is a Daemon cron task, CommunicationLogDelete, which runs daily. What is deleted can be configured with the settings CommunicationLog::PurgeAfterHours::SuccessfulCommunications and CommunicationLog::PurgeAfterHours::AllCommunications

By executing the command bin/otrs.Console.pl Maint::Log::CommunicationLog you can also delete entries manually.

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
Post Reply