Hi, Here is the result of the command actually tables "audit_log" are very large . What can I do to prevent the file system fills up? psql engine -c "SELECT nspname || '.' || relname AS relation, pg_size_pretty(pg_relation_size(C.oid)) AS size FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE nspname NOT IN ('pg_catalog', 'information_schema') ORDER BY pg_relation_size(C.oid) DESC LIMIT 20;" relation | size ------------------------------------------+--------- public.audit_log | 826 MB public.idx_audit_correlation_id | 159 MB public.idx_audit_log_job_id | 114 MB public.idx_audit_log_storage_domain_name | 114 MB public.idx_audit_log_user_name | 114 MB public.idx_audit_log_vm_name | 114 MB public.idx_audit_log_storage_pool_name | 114 MB public.idx_audit_log_vds_name | 114 MB public.idx_audit_log_vm_template_name | 113 MB public.pk_audit_log | 90 MB public.idx_audit_log_log_time | 90 MB pg_toast.pg_toast_2618 | 1336 kB public.vm_dynamic | 680 kB public.vm_statistics | 496 kB public.disk_image_dynamic | 288 kB public.vds_interface_statistics | 256 kB public.vm_device | 208 kB public.vds_dynamic | 128 kB pg_toast.pg_toast_2619 | 120 kB public.pk_disk_image_dynamic | 104 kB (20 rows) Regards Massimo
----- Original Message -----
From: "Massimo Mad" <mad1969it@gmail.com> To: users@ovirt.org Sent: Wednesday, February 25, 2015 11:14:28 AM Subject: [ovirt-users] oVirt Manager problem
Hi, Here is the result of the command actually tables " audit_log " are very large . What can I do to prevent the file system fills up ?
It seems that the total objects (tables and indices) around audit_log table is 2GB. You can control the number of entries in this table by setting a shorter period for keeping data in that table. The default is 30 days. You can check by: engine-config -g AuditLogAgingThreshold and if wish to set a smaller value for days to keep, i.e for a week: engine-config -s AuditLogAgingThreshold=7 and restart the ovirt-engine to take effect. However, I'm curious if there is some flooding of a certain event-log entry in that table which might cause this table to increase to that volume unless it reflects the actual workload of the system.
psql engine -c "SELECT nspname || '.' || relname AS relation, pg_size_pretty(pg_relation_size(C.oid)) AS size FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE nspname NOT IN ('pg_catalog', 'information_schema') ORDER BY pg_relation_size(C.oid) DESC LIMIT 20;"
relation | size ------------------------------------------+--------- public.audit_log | 826 MB public.idx_audit_correlation_id | 159 MB public.idx_audit_log_job_id | 114 MB public.idx_audit_log_storage_domain_name | 114 MB public.idx_audit_log_user_name | 114 MB public.idx_audit_log_vm_name | 114 MB public.idx_audit_log_storage_pool_name | 114 MB public.idx_audit_log_vds_name | 114 MB public.idx_audit_log_vm_template_name | 113 MB public.pk_audit_log | 90 MB public.idx_audit_log_log_time | 90 MB pg_toast.pg_toast_2618 | 1336 kB public.vm_dynamic | 680 kB public.vm_statistics | 496 kB public.disk_image_dynamic | 288 kB public.vds_interface_statistics | 256 kB public.vm_device | 208 kB public.vds_dynamic | 128 kB pg_toast.pg_toast_2619 | 120 kB public.pk_disk_image_dynamic | 104 kB (20 rows)
Regards Massimo
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Massimo Mad -
Moti Asayag