Hello Joe, Good to hear that the memory leak was fixed in the 1.6 series.
One more question remains: Is there any way to increase the log level of the audit component of the nifi-ranger-plugin? Thanks Johannes -----Ursprüngliche Nachricht----- Von: Joe Witt <joe.w...@gmail.com> Gesendet: Montag, 7. Mai 2018 15:00 An: users@nifi.apache.org Betreff: Re: Improving Ranger audit logging in Nifi Hello I suspect you're on a version older than the latest (1.6.0). This was resolved in the latest release https://issues.apache.org/jira/browse/NIFI-4925 Thanks Joe On Mon, May 7, 2018 at 8:50 AM, <johannes.meix...@post.ch> wrote: > We’re using Ranger to provide LDAP group-based authorization to NiFi > resources via the Ranger-NiFi plugin. This works well, and read-only / > read-write access can be defined quite granularly. > > > > Audit logs are written into Solr in order for us to search them using > Ranger GUI later on. This worked fine until Friday, upon which “something > changed” > (NiFi was restarded without changes) and the connection between > nifi-ranger-plugin and Solr was interrupted. > > > > Today, then, Nifi’s Heap Usage went through the roof up to 97%, most > of which ConcurrentHashMaps spawned by ManagedRangerAuthorizer. > > > > We’ve noticed this type of memory leak in the past: previously, > ranger-nifi-plugin failed to send resources to Solr due to a mismatch > in SSL FQDNs. > > > > This could be solved by setting SOLR_HOST=`hostname –f` in the > infra-solr-env template, but the logging of the > ManagedRangerAuthorizer and its batch transmitting to Solr is rather… shall > we say… parsimonious. > > > > How do I increase it so I can actually see what’s causing the memory > leak in Ranger/NiFi/Solr interactions? > > > > > > Regards, > > > > > > > > Johannes Meixner > > Post CH AG > Informationstechnologie > > DWH & Big Data Solutions > Webergutstrasse 5 > 3030 Bern (Zollikofen) > > Internet: http://www.post.ch > > Tel.: +41 58 341 40 77 > >
