[NIFI-6895] PutKudu Processor Warnings - Applying an operation in a closed session; this is unsafe

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.11.0
• Environment: Kudu 1.10.0; NiFi 1.10.0, OpenJDK 8 (232); 8 Node Cluster
• Assignee: Grant Henke
• Reporter: Josef Zahner
• Created: 21/Nov/19 11:02
• Updated: 31/Jan/20 11:06
• Resolved: 03/Dec/19 02:47

Description

We have just upgraded from NiFi 1.9.2 to NiFi 1.10.0. We have seen that we got 1’000 times more logs (nifi-app.log) since the upgrade, caused mainly by the PutKudu processor.

The logmessages we are always getting are: 

2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-2] org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe

The PutKudu processor itself seems to work fine.

 

The line of code which from Apache Kudu Client which reflects the message is here: (line 547):
https://github.com/apache/kudu/blob/master/java/kudu-client/src/main/java/org/apache/kudu/client/AsyncKuduSession.java

 

Since we are getting a huge amount of loglines we had to insert the following workaround in logback.xml:

<logger name="org.apache.kudu.client.AsyncKuduSession" level="ERROR"/>

Without suppressing the AsyncKuduSession messages we are getting multiple gigabytes of data per hour, but sadly with the workaround we don't see any PutKudu warnings anymore. 

 

Can the dev's please check why we are getting the warning and fix the root cause? Thanks in advance.

Issue Links

• is duplicated by: NIFI-6908 PutKudu 1.10.0 Memory Leak
• is related to: KUDU-3012 Throttle "Applying an operation in a closed session" warning log
• links to: GitHub Pull Request #3910