Audit data would have more bearing on the disk space than policy data stored in DB. You would need to make sure you can purge audit after regular intervals. Alternative is to use Solr and HDFS to store audit, Ranger UI can query from Solr.
On Tue, Jan 12, 2016 at 11:45 AM, Madhan Neethiraj <[email protected]> wrote: > Lune, > > 1 GB of storage for policy store seems reasonable. Audit DB store sizing > will depend on the volume of audits in a deployment. Looking at the audit > table definition (xa_access_audit), the *maximum size* of each row is > around 12k bytes; however most audit records will likely to require much > smaller space. You can use the max row size for sizing purposes. > > Hope this helps. > > Thanks, > Madhan > > From: Lune Silver <[email protected]> > Reply-To: "[email protected]" < > [email protected]> > Date: Tuesday, January 12, 2016 at 7:14 AM > To: "[email protected]" <[email protected]> > Subject: A question relative to the ranger database > > Hello ! > > I send this ticket because I have a sizing question related to the > database used to store administration information for ranger. > > I have a postgresql database.Do you know what is the sizing to expect for > the administration db ? Is 1 GB enough ? Or is it more like 10 GB ? > > As a note, while I am studying the addition of solR to take care of the > audit, I will for the moment store : > - a few days of audit in another postgresql db > - a few month in hdfs > > Best regards. > > Lune. > > >
