You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Eduardo Mota Fontes (Jira)" <ji...@apache.org> on 2021/11/25 02:08:00 UTC
[jira] [Updated] (MINIFICPP-1692) Thread stucks on OnTrigger
[ https://issues.apache.org/jira/browse/MINIFICPP-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eduardo Mota Fontes updated MINIFICPP-1692:
-------------------------------------------
Description:
I've tested minifi 0.11 + Nifi 1.15 and I got warnings that I don't know if it's a version issue.
How to reproduce:
- Download and unpack Nifi 1.15 binary
- Download, unpack and compile Minifi 0.11 source
- Start Nifi with default settings, create a remote input port with name "entrada", start it and connect it to a funnel
- Configure minifi TLS
- Configure minifi's flow (config.yaml) with a ExecuteCommand (find ./ each 30 secs) with success relationship to a RPG pointing to NiFi 1.15 "entrada" input port
- Start minifi
At this point everything is ok. The result of the command "find ./" lands on the NiFi input port and stays in the funnel's queue.
The problem is, if NiFi stops for some reason (I simulate this stopping the input port), I start to get warnings in minifi's log the like:
[org::apache::nifi::minifi::SchedulingAgent] [warning] entrada::onTrigger has been running for 971026 ms in 4d3e32ac-017d-1000-b4b1-e7f36e039202
And if I start NiFi the warnings continue and it never stops. In this state, if I try to stop minifi using "minifi.sh stop" it doesn't stop and I have to kill the minifi's process.
It seems the thread stuck.
I did the same test with 0.10 minifi c++ and the issue doesn't happen. When I stop the input port in NiFi I get this:
[org::apache::nifi::minifi::core::Processor] [warning] Caught "Process Session Operation: Can not find the transfer relationship for the updated flow 89289e16-4d90-11ec-bef4-c0b6f9f714b7" (N3org6apache4nifi6minifi9ExceptionE) during Processor::onTrigger of processor: 4d3e32ac-017d-1000-b4b1-e7f36e039202 (entrada)
And when I started the input port again it came back to work normally.
The issue doesn't happen with MiNiFi 1.15 Java version too.
Config e log attached.
PS.: See the logs from 5000+ line. Before this is trash. Sorry
was:
I've tested minifi 0.11 + Nifi 1.15 and I got warnings that I don't know if it's a version issue.
How to reproduce:
- Download and unpack Nifi 1.15 binary
- Download, unpack and compile Minifi 0.11 source
- Start Nifi with default settings, create a remote input port with name "entrada", start it and connect it to a funnel
- Configure minifi TLS
- Configure minifi's flow (config.yaml) with a ExecuteCommand (find ./ each 30 secs) with success relationship to a RPG pointing to NiFi 1.15 "entrada" input port
- Start minifi
At this point everything is ok. The result of the command "find ./" lands on the NiFi input port and stays in the funnel's queue.
The problem is, if NiFi stops for some reason (I simulate this stopping the input port), I start to get warnings in minifi's log the like:
[org::apache::nifi::minifi::SchedulingAgent] [warning] entrada::onTrigger has been running for 971026 ms in 4d3e32ac-017d-1000-b4b1-e7f36e039202
And if I start NiFi the warnings continue and it never stops. In this state, if I try to stop minifi using "minifi.sh stop" it doesn't stop and I have to kill the minifi's process.
It seems the thread stuck.
I did the same test with 0.10 minifi c++ and the issue doesn't happen. When I stop the input port in NiFi I get this:
[org::apache::nifi::minifi::core::Processor] [warning] Caught "Process Session Operation: Can not find the transfer relationship for the updated flow 89289e16-4d90-11ec-bef4-c0b6f9f714b7" (N3org6apache4nifi6minifi9ExceptionE) during Processor::onTrigger of processor: 4d3e32ac-017d-1000-b4b1-e7f36e039202 (entrada)
And when I started the input port again it came back to work normally.
The issue doesn't happen with MiNiFi 1.15 Java version too.
Config e log attached.
> Thread stucks on OnTrigger
> ---------------------------
>
> Key: MINIFICPP-1692
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1692
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Affects Versions: 0.11.0
> Reporter: Eduardo Mota Fontes
> Priority: Major
> Attachments: config.yml, minifi-app.log, minifi.properties
>
>
> I've tested minifi 0.11 + Nifi 1.15 and I got warnings that I don't know if it's a version issue.
> How to reproduce:
> - Download and unpack Nifi 1.15 binary
> - Download, unpack and compile Minifi 0.11 source
> - Start Nifi with default settings, create a remote input port with name "entrada", start it and connect it to a funnel
> - Configure minifi TLS
> - Configure minifi's flow (config.yaml) with a ExecuteCommand (find ./ each 30 secs) with success relationship to a RPG pointing to NiFi 1.15 "entrada" input port
> - Start minifi
> At this point everything is ok. The result of the command "find ./" lands on the NiFi input port and stays in the funnel's queue.
> The problem is, if NiFi stops for some reason (I simulate this stopping the input port), I start to get warnings in minifi's log the like:
> [org::apache::nifi::minifi::SchedulingAgent] [warning] entrada::onTrigger has been running for 971026 ms in 4d3e32ac-017d-1000-b4b1-e7f36e039202
> And if I start NiFi the warnings continue and it never stops. In this state, if I try to stop minifi using "minifi.sh stop" it doesn't stop and I have to kill the minifi's process.
> It seems the thread stuck.
> I did the same test with 0.10 minifi c++ and the issue doesn't happen. When I stop the input port in NiFi I get this:
> [org::apache::nifi::minifi::core::Processor] [warning] Caught "Process Session Operation: Can not find the transfer relationship for the updated flow 89289e16-4d90-11ec-bef4-c0b6f9f714b7" (N3org6apache4nifi6minifi9ExceptionE) during Processor::onTrigger of processor: 4d3e32ac-017d-1000-b4b1-e7f36e039202 (entrada)
> And when I started the input port again it came back to work normally.
> The issue doesn't happen with MiNiFi 1.15 Java version too.
>
> Config e log attached.
> PS.: See the logs from 5000+ line. Before this is trash. Sorry
--
This message was sent by Atlassian Jira
(v8.20.1#820001)