[ 
https://issues.apache.org/jira/browse/NIFI-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527177#comment-16527177
 ] 

Ahmed edited comment on NIFI-5347 at 6/29/18 4:38 AM:
------------------------------------------------------

Additionally i would like to update what we noticed recently.

If the files in HDFS are there for sometime like a day or so & we run the 
GETHDFS processor, it instantly takes the file (how many ever times we run , it 
successfully completes.)

If the same is done on newly added files in HDFS it is making the processor in 
hung or not passing it to next processor until some time is passed for the file 
laying in that path in HDFS.

Let me know if more details required.


was (Author: big-d):
Additionally i would like to update what we noticed recently.

If the files in HDFS are there for sometime like a day or so & we run the 
GETHDFS processor, it instantly takes the file (how many ever times we run , it 
successfully completes.)

If the same is done on newly added files in HDFS it is making the processor in 
hung or not passing it to next processor.

Let me know if more details required.

> 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
(v7.6.3#76005)

Reply via email to