[Spacewalk-list] Spacewalk - PostgreSQL High I/O

[Matt Moldvan]

I had similar issues and ended up first breaking out the database to it's
own VM, then increasing the Postgres debug logs.  I saw that there were a
large number of operations running against the snapshot tables, with locks
and so on being set for a long period of time.  In /etc/rhn/rhn.conf, try
disabling snapshots with:

enable_snapshots = 0

I also did quite a bit of Postgres tuning using pgtune, for 5,000 clients
or so:
pgtune -i data/postgresql.conf  -o ./data/postgresql.conf.new -c 5000

Another thing that may help is installing pgbadger to analyze your Postgres
logs... it has some nice visualizations of the types of queries and tables
involved, which may point you in the right direction if snapshots aren't
the reason for the high utilization.
https://github.com/dalibo/pgbadger

Hope that helps.

On Mon, Oct 10, 2016 at 4:06 PM Konstantin Raskoshnyi <konrasko at gmail.com>
wrote:

> Because all your systems request information from SP, and default
> installation doesn't make any sense if you have more that 50 machines, so
> you need to tyne postgres, tomcat & linux itself
>
> On Mon, Oct 10, 2016 at 12:34 PM, Allan Moraes <allan at allanmoraes.com.br>
> wrote:
>
> Hi
> In my CentOS 7 server, is installed the spacewalk 2.4 and PostgreSQL from
> default installation. Via iotop, my postgresql write a lot of informations,
> during all day. Why this occur?
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20161010/6f9c7430/attachment.htm>