@Shmoo @mszurap By any chance do you have any insights here? Thanks! ... View more

@Amn_468 Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

@KundanRND Welcome to the Cloudera Community! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

@robdisseldorp Welcome to the Cloudera Community! To help you get the best possible solution, I have tagged our NiFi expert @steven-matison  who may be able to assist you further. Please keep us updated on your post, and we hope you find a satisfactory solution to your query. ... View more

@Seaport Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. If you are still experiencing the issue, can you provide the information @ezerihun has requested? Thanks. ... View more

Thanks Diana! I just came on to post what we found for any future folks searching for a similar issue. It looks like this was potentially a client issue. We found this in the JDBC driver change log for 2.6.20 and it seemed to match the behavior we are seeing. [00265194][IMPJ-606 ] When the server returns 0 rows, the driver stops fetching results. We have updated our clients and have not been able to reproduce the issue. Presumably when the client incorrectly closes the connection, the server stops processing wherever it happens to be, which is why we see it stopping before the 100%. This is more of a symptom than the cause.  ... View more

@Sergeii Welcome to the Cloudera Community! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

Thanks a lot! @cotopaul  Solution 1 worked in our case. We stopped our processors and emptied queues, after that moving the connection from center funnel to the new processor helped us to remove other funnels. To answer your question, why the infinite loop ? it was effect of blunder - when I was working with the funnels weren't located so sparsely, so I didn't see that the connection I'm going to make and created a loop ... View more

@user001, I do not know what your Sandbox environment is, but I just tested with NiFi 1.15 and the solution works like a charm. So either you are doing something wrong, or you have something configured incorrectly in your sandbox environment. Or maybe NiFI 1.18 is bugged - but I highly doubt it, as there would have been far more posts reporting similar issues. ... View more