You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2023/03/30 17:10:00 UTC
[jira] [Resolved] (NIFI-5347) Nifi - GETHDFS processor not able to find the files in HDFS / Processor is getting stuck
[ https://issues.apache.org/jira/browse/NIFI-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Witt resolved NIFI-5347.
----------------------------
Resolution: Information Provided
Hello. This implies the 'modification time' of the files is in the future or less than the configured 'min age' which by default is 0. Please update min age or modification date and it will see the files immediately.
> Nifi - GETHDFS processor not able to find the files in HDFS / Processor is getting stuck
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-5347
> URL: https://issues.apache.org/jira/browse/NIFI-5347
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.6.0
> Reporter: Ahmed
> Priority: Major
> Attachments: nifi-app.log, text
>
>
> Hi
> Nifi GETHDFS processor gets stuck/hung or not able to idnentify the files in HDFS directory.
> While i let the process to keep retrying multiple times with a schedule state of retry in every 0 second, the processor identifies the file after 300-400 retries.
> Sharing the log information below:
> 2018-06-28 11:47:15,853 INFO [NiFi Web Server-100] o.a.n.c.s.StandardProcessScheduler Starting GetHDFS[id=809d3a14-f0ec-1e4f-ca1e-9fbce341b4f5]
> 2018-06-28 11:47:15,896 INFO [Monitor Processore Lifecycle Thread-1] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled GetHDFS[id=809d3a14-f0ec-1e4f-ca1e-9fbce341b4f5] to run with 1 threads
> 2018-06-28 11:47:16,214 INFO [Flow Service Tasks Thread-2] o.a.nifi.controller.StandardFlowService Saved flow controller org.apache.nifi.controller.FlowController@33dbd739 // Another save pending = false
>
> Earlier this was working smooth, the issue is noticed after we restarted the nifi restart? Could somebody help with the unexpected behaviour or issue noticed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)