You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2018/06/28 12:43:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16526274#comment-16526274 ]
Joseph Witt commented on NIFI-5347:
-----------------------------------
please do a thread dump for nifi when it appears stuck
bin/nifi.sh dump
Then share the logs dir in a zip archive.
Thanks
> 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
>
> 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
(v7.6.3#76005)