nav_audit grows quite large in size as compared to other databases under CM

[#1]

Hi,

We have seen few of our clusters getting affected because ibdata1 under mysql grows too large to occupy all the disk. On further checking it was nav_audt DB under CM databases which occupied all the space. Could this be because of BDR setup in the environment and if thats the case how can this be avoided. As a workaround,we are just changing the retention period for nav audits in CM.

Thanks

Pravdeep

[#2]

Hi Praveep,

Disk usage on Navigator audit is based on the audit events occurring in the cluster as a whole, and BDR will only contribute a select percentage of this (the exact value will differ between environments). Typically Navigator audit/metadata disk usage is many times greater than other Cloudera Manager Management components and you should provision disk space accordingly. Please see our documentation for additional assistance scoping your disk requirements, and for the components which contribute audits:

http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_reqs_space.html

Thanks,

MJ

[#3 · Accepted solution]

Hi,

Thanks for your response, we eventually found out the reason upon checking the tables under nav_audit database which were loaded with getfacl records under them. We changed the regex to avoid logging getfacls and decreased the timepeiord to retain nav audits to 30 instead of 90(default) to bring down the disk usage of this database.

Thanks & Regards

Pravdeep

[#4]

Hi, 

Could you please provide the steps.

Thanks 

[#5]

Hi Pravi,
Please review the documentation here: https://docs.cloudera.com/documentation/enterprise/latest/topics/cn_admcfg_audit_filters.html

and let us know if you have any questions.

Thanks,

MJ