Hi Jean, Out of curiosity, is it a NiFi cluster (if yes, of how many nodes?) or a standalone node?
Pierre 2018-07-09 8:51 GMT+02:00 GASCHLER, Jean <[email protected]>: > Yes. Here it is. > > > > But the problem appears in other places in my NiFi. > > > > > > *De :* Sivaprasanna [mailto:[email protected]] > *Envoyé :* lundi 9 juillet 2018 08:30 > *À :* [email protected] > *Cc :* Mark Payne > > *Objet :* Re: Nifi 1.7.0: queue is stuck for no reason > > > > Execution is fine. Can you please share the screenshot of the "Properties" > tab of the ReplaceText processor (Replace Special Characters)? > > > > On Mon, Jul 9, 2018 at 11:12 AM GASCHLER, Jean < > [email protected]> wrote: > > Hi Mark > > > > Here is the screenshot of the Scheduling Tab. The scheduling seems OK and > no changes have been done since NiFi version 1.6.0. Nevertheless I > discovered the new field “Execution” but I didn’t change its default value. > So dump is in attachement. > > Thanks for your help. > > > > [image: cid:[email protected]] > > > > Bien cordialement - Best Regards - Freundlichen Grüßen – Cordiali > saluti - Vljudno - Pozdrawiam - 亲切的问候 - με φιλικούς χαιρετισμούς > > _______________________________________________________________________ > > [image: Email_CBE.gif]*Jean Gaschler * > > Architecte IT | PER PU Est > > DP Rhône-Alpes-Auvergne | CHSCT > > > > Capgemini Technology Services SAS > > 95 chemin de l'étoile > <https://maps.google.com/?q=95+chemin+de+l'%C3%A9toile+%0D%0A+38330+Montbonnot+Saint+Martin&entry=gmail&source=g> > > 38330 Montbonnot Saint Martin > <https://maps.google.com/?q=95+chemin+de+l'%C3%A9toile+%0D%0A+38330+Montbonnot+Saint+Martin&entry=gmail&source=g> > > Tel.: +33 (0)476 39 9584 > > Accueil standard: +33 (0)476 39 9400 > > Fax: +33 (0)476 39 9401 > > > > [image: Email_CBE.gif] > _______________________________________________________________________ > > *Connect with Capgemini:* > [image: cid:[email protected]] > <http://www.capgemini.com/insights-and-resources/blogs>[image: > cid:[email protected]] <http://www.twitter.com/capgemini>[image: > cid:[email protected]] <http://www.facebook.com/capgemini>[image: > cid:[email protected]] > <http://www.linkedin.com/company/capgemini>[image: > cid:[email protected]] > <http://www.slideshare.net/capgemini>[image: > cid:[email protected]] > <http://www.youtube.com/capgeminimedia> > > > > Please consider the environment and do not print this email unless > absolutely necessary. > > Capgemini encourages environmental awareness. > > > > *De :* Mark Payne [mailto:[email protected]] > *Envoyé :* dimanche 8 juillet 2018 13:51 > *À :* [email protected] > *Objet :* Re: Nifi 1.7.0: queue is stuck for no reason > > > > Hi Jean, > > > > It looks like the ReplaceText processor is not getting scheduled to run. > Can you include a screenshot of the processor’s configuration- specifically > the Scheduling Tab? > > > > Also can you gather a thread dump? You can get this by running > “bin/nifi.sh dump thread-dump.txt” > > > > Thanks > > Sent from my iPhone > > > On Jul 8, 2018, at 6:25 AM, GASCHLER, Jean <[email protected]> > wrote: > > Hi > > > > I have migrated from NiFi 1.6.0 to 1.7.0 in order to solve some problems > with the PutMongoRecord processor. > > I have now a problem with queues which are stuck without any errors in the > logs (especially when they are after an Input Port). > > For example, > > <image011.png><image010.png> > > > > The configuration of this queue example is the following: > > <image012.png><image013.png> > > > > Any idea? > > Thanks > > Bien cordialement - Best Regards - Freundlichen Grüßen – Cordiali > saluti - Vljudno - Pozdrawiam - 亲切的问候 - με φιλικούς χαιρετισμούς > > _______________________________________________________________________ > > <image001.gif>*Jean Gaschler * > > > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. > >
