Nifi 1.16.3 updates and bugs used in production.

order

The company is responsible for NiFi Clusters are almost 50+. Half of the clusters are from 1.15.2 Upgrade to 1.16.3 edition , Average upgrade time 5min about , Some capacity expansion operations are also involved . But if you rely on ambari Or other management platforms will definitely spend more time .

Update Texin

https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.3

Personal experience

• Finally put HDFS Connection related has been updated , promote hdfs-client Version to 3.3, Fixed many versions , Finally, there is no need to create so many safe threads ：
  

• 1.16.X Updated flow.json, Indeed, the writing speed is faster , The volume is reduced by half ：
  but The present judgment condition is flow.json/xml . But it also introduces a new bug： stay cluster in , If it's time to node No, flow.json/xml Words , This node will not be created when it is started flow.json, And comparing with cluster Medium flow.json I will report java.lang.NullPointerException problem . So it needs to be done manually copy One , Or start a single node and then join the cluster .

• listFTP to update , Developed several classes , Solve various problems caused by agents ：
  but New bug, Lead to username/userpassword/ftp_ip Cannot use variable , Need to repack standard, And update and restart the cluster .

• Many high-risk vulnerabilities have been solved , But it didn't solve apache common configuration, Several packages are involved , contain frameword package , Again nar package , Rely on .

• added retry, I prefer this one .

expect

• Follow knox Cooperate better , It's really a painful process to build .
• minifi The experience of using is really bad , If you're out of it CEP It can only be used like this , It is suggested to give priority to the development of similar CEP Management tools .