Re: PutKudu 1.10.0 Processor generates tons of log warnings - org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe
Thank you Pierre, your workaround works like a charm! JIRA request has been created: https://issues.apache.org/jira/projects/NIFI/issues/NIFI-6895 From: Pierre Villard Reply to: "users@nifi.apache.org" Date: Thursday, 21 November 2019 at 10:52 To: "users@nifi.apache.org" Subject: Re: PutKudu 1.10.0 Processor generates tons of log warnings - org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe Hi Joseph, Yes please file a JIRA, we need to have a look even though it might be due to a version change in the Kudu dependency. To workaround the issue, adding the below line into logback.xml should fix it: Hope this helps, Pierre Le jeu. 21 nov. 2019 à 10:33, mailto:josef.zahn...@swisscom.com>> a écrit : Hi guys We have just upgraded to NiFi 1.10.0 yesterday. We have seen that we got 1’000 times more logs (nifi-app.log) since the upgrade, caused mainly by the PutKudu processor. The logmessage we always get is: 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 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe 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 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe … The PutKudu processor itself seems to work fine. We have the same amount of inserts as before the upgrade to NiFi 1.10.0. The line of code which from Apache Kudu 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 Questions: 1. How can I suppress just this single type of warning in NiFi? Most likely in logback.xml – but is there any tutorial how to do this? The messages generates multiple gigabytes of logs on our nodes per hour… we have to get rid of this kind of message as soon as possible. 2. Seems that from NiFi 1.9.2 to NiFi 1.10.0 something has changed in the PutKudu processor, we haven’t seen this message before. Shall I fill a jira ticket for that? Or has anybody an idea? Thanks in advance, Josef smime.p7s Description: S/MIME Cryptographic Signature
Re: PutKudu 1.10.0 Processor generates tons of log warnings - org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe
Hi Joseph, Yes please file a JIRA, we need to have a look even though it might be due to a version change in the Kudu dependency. To workaround the issue, adding the below line into logback.xml should fix it: Hope this helps, Pierre Le jeu. 21 nov. 2019 à 10:33, a écrit : > Hi guys > > > > We have just upgraded to NiFi *1.10.0* yesterday. We have seen that we > got 1’000 times more logs (nifi-app.log) since the upgrade, caused mainly > by the *PutKudu* processor. > > > > The logmessage we always get is: > > 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 > > 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] > org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed > session; this is unsafe > > 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 > > 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] > org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed > session; this is unsafe > > … > > > > The PutKudu processor itself seems to work fine. We have the same amount > of inserts as before the upgrade to NiFi 1.10.0. > > > > The line of code which from Apache Kudu 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 > > > > *Questions:* > >1. How can I suppress just this single type of warning in NiFi? Most >likely in logback.xml – but is there any tutorial how to do this? The >messages generates multiple gigabytes of logs on our nodes per hour… we >have to get rid of this kind of message as soon as possible. >2. Seems that from NiFi 1.9.2 to NiFi 1.10.0 something has changed in >the PutKudu processor, we haven’t seen this message before. Shall I fill a >jira ticket for that? Or has anybody an idea? > > > > Thanks in advance, > > Josef > > >
PutKudu 1.10.0 Processor generates tons of log warnings - org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe
Hi guys We have just upgraded to NiFi 1.10.0 yesterday. We have seen that we got 1’000 times more logs (nifi-app.log) since the upgrade, caused mainly by the PutKudu processor. The logmessage we always get is: 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 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe 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 2019-11-21 08:42:27,627 WARN [Timer-Driven Process Thread-40] org.apache.kudu.client.AsyncKuduSession Applying an operation in a closed session; this is unsafe … The PutKudu processor itself seems to work fine. We have the same amount of inserts as before the upgrade to NiFi 1.10.0. The line of code which from Apache Kudu 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 Questions: 1. How can I suppress just this single type of warning in NiFi? Most likely in logback.xml – but is there any tutorial how to do this? The messages generates multiple gigabytes of logs on our nodes per hour… we have to get rid of this kind of message as soon as possible. 2. Seems that from NiFi 1.9.2 to NiFi 1.10.0 something has changed in the PutKudu processor, we haven’t seen this message before. Shall I fill a jira ticket for that? Or has anybody an idea? Thanks in advance, Josef smime.p7s Description: S/MIME Cryptographic Signature
