Member since
04-02-2015
10
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4456 | 07-24-2020 02:39 AM |
01-16-2022
11:42 PM
Hello, problem was with OOO memory, after add some, it looks ok. Thank for advice. Best regards Kamil
... View more
02-05-2021
06:25 AM
1 Kudo
@Kamil_Valko All NiFi logging is handled by the logback.xml file. By default you will find that NiFi's logback.xml contains three unique file appenders. 1. APP_FILE 2. USER_FILE 3. BOOTSTRAP_FILE. To log anything to a different file, the first thing to do is create another appender. I recommend copying the APP_FILE appender. <appender name="FTP_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/var/log/nifi/nifi-ftp.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
<fileNamePattern>/var/log/nifi/nifi-ftp_%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern>
<maxFileSize>100MB</maxFileSize>
<maxHistory>5</maxHistory>
<totalSizeCap>1GB</totalSizeCap>
</rollingPolicy>
<immediateFlush>true</immediateFlush>
<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
<pattern>%date %level [%thread] %logger{40} %msg%n</pattern>
</encoder>
</appender> Then you need to add a new logger for the FetchFTP processor class. You cannot control logging for specific instance of a processor. This means all logging from all instantiations of the listFTP processor on the canvas will get handled by this new logger. <logger name="org.apache.nifi.processors.standard.FetchFTP" level="ERROR" additivity="false">
<appender-ref ref="FTP_FILE"/>
</logger> You can turn off logging for a specific processor class, but I agree with @ckumar that this is not an ideal path. But for completeness of this response, setting level to "OFF" on a logger for a specific class will stop all logging from that class. (Remember that this affects logging from all occurrences of this processor used by this NiFi) Hope this helps, Matt
... View more
07-24-2020
03:32 AM
Policy is synced to all the nodes. You can check that in Ranger->Audit->Plugins. If not, then you should check if you have access policy for node identities,
... View more