Re: Flow File Stuck for no reason

Hello This part of the stack dump is the only thing that appears out of place to me. it appears to be attempting to read from the socket or stuck there. Perhaps you can use a more recent client library for that custom HD processor? "Timer-Driven Process Thread-8" Id=78 RUNNABLE (in native

Re: Flow File Stuck for no reason

Manish, Ok what I am saying is that NIFI-1922 was simply trying to add one dependency into the HDFS processors to make the Azure file system implementations available: org.apache.hadoop hadoop-azure 2.7.2+ In NiFi 1.1 this is no longer necessary because the HDFS processors have a property

Re: Flow File Stuck for no reason

Bryan, It's for uploading data on HDInsight cluster and as per the patch in Nifi-1922. Regards, Manish On Thu, Dec 1, 2016 at 12:16 PM, Bryan Bende wrote: > Manish, > > Was the reason for your custom version of PutHDFS just to include the > Azure libraries? or was there

Re: Flow File Stuck for no reason

manish my apologies now I see what you mean. It is 0.7.0 nifi and you have a custom nar that is 1.0.0 which is totally fine. Bryan's response though is a good one to follow up on. Thanks joe On Thu, Dec 1, 2016 at 9:16 AM, Bryan Bende wrote: > Manish, > > Was the reason for

Re: Flow File Stuck for no reason

Manish, Was the reason for your custom version of PutHDFS just to include the Azure libraries? or was there other functionality you needed to introduce? The reason I'm asking is because in the Apache NiFi 1.1 release (just released) we added an "Additional Classpath Resources" property to all

Re: Flow File Stuck for no reason

Manish It also appears from the log output you provided so far that this is a combination of nifi 0.7 and 1.0 parts. We do not recommend doing this and it is not likely to work. Please try the flow from a single release line. Apache NiFi 1.1.0 is available for use now. Thanks Joe On Thu, Dec

Re: Flow File Stuck for no reason

Got it. I was not aware of "bin/nifi.sh dump". I will try that once I see the issue again. Thanks, Manish On Thu, Dec 1, 2016 at 11:59 AM, Joe Witt wrote: > Manish > > When it is in the stuck state can you please run > bin/nifi.sh dump. If you can then share the

Re: Flow File Stuck for no reason

Manish When it is in the stuck state can you please run bin/nifi.sh dump. If you can then share the nifi-bootstrap.log that would aid us in narrowing in on a possible cause. Thanks Joe On Thu, Dec 1, 2016 at 8:44 AM, Manish G wrote: > Hi Joe, > > Here is what I can see

Re: Flow File Stuck for no reason

Hi Joe, Here is what I can see in the App Log: 2016-12-01 09:28:52,004 ERROR [Timer-Driven Process Thread-4] testing.nifi.processor.hdfs.testingPutHDFS "" org.apache.hadoop.fs.azure.AzureException: java.util.NoSuchElementException: An error occurred while enumerating the result, check the

Re: Flow File Stuck for no reason

Manish Please produce and share the thread dump I mentioned. Thanks Joe On Dec 1, 2016 7:23 AM, "Manish G" wrote: > Hi, > > I don't know why, but this is happening now more frequently. Where should > I look into to find the root cause? > > Thanks, > Manish > > On Wed,

Re: Flow File Stuck for no reason

Hi, I don't know why, but this is happening now more frequently. Where should I look into to find the root cause? Thanks, Manish On Wed, Nov 30, 2016 at 9:20 PM, Manish G wrote: > Hi Joe, > > Thanks for the quick reply. Yes, the processor keeps running on a single >

Re: Flow File Stuck for no reason

Hi Joe, Thanks for the quick reply. Yes, the processor keeps running on a single thread (even after stopping). And the number remains there even after stopping. Today, it happened on my customized putHDFS processor. Only thing different in this processor is - I have added an additional attribute