About abhinav_joshi

abhinav_joshi · ‎04-08-2019

HI Matt , Thanks for your answer. I am attaching the screen shot below . You can see how just the " Update Attribute" seems to have those dashed lines and is in "invalid" state. I doubt think our developers made any custom change to the update attribute processor. Let me know what you think about this meanwhile I have looked at the app.log and can see this error You were bang on when you said about the 'Ghost' Implementation. What do you think should be the next steps -bash-4.2$ cat nifi-app-*.log |grep "Unable to find bundle for coordinate" Caused by: java.lang.IllegalStateException: Unable to find bundle for coordinate org.apache.nifi:nifi-update-attribute-nar:1.8.0 ERROR [main] o.a.nifi.controller.ExtensionBuilder Could not create Processor of type org.apache.nifi.processors.attributes.UpdateAttribute for ID 629d355f-0167-1000-ffff-ffffbc497b67; creating "Ghost" implementation

abhinav_joshi · ‎04-08-2019

Hi Matt , for the existing flow , the "update attribute" processor was in an inconfigurable state i.e it had this dotted line all over it and when I clicked on it it wasnt showing anything. This has happened for all the "update attribute" processors in our flow. For now , we have had to delete this processor and add a new one and add configur it. We also realize that the new "update attribute" processor has an extra feature with version 1.9 which wasnt available in 1.8. However this should be taken care of automatically with an upgrade.

abhinav_joshi · ‎04-08-2019

Update Attribute processor Not working after upgrade from version 1.8 to version 1.9. We recently upgraded our Nifi Cluster from version 1.8 to version 1.9 and we were surprised to see the update attribute processor all going invalid for our existing flows. We had to manually fix the existing flow but this ideally should have been handled with the upgrade . Is there a way to overcome this ?

abhinav_joshi · ‎02-25-2019

For now we set the nifi.queue.swap.threshold to 150000 and this seems to have done the trick. Loads are performing well and there is no build up of the queue. thanks all

abhinav_joshi · ‎02-24-2019

Hi All, We have just productionized our Nifi flows which is a real time streaming application . We have a cluster of 2 Nodes and each node has 6 processors and a high memory of 28 GB. On the Nifi side the memory has been set to 24 GB. Moreover , we tend to see a queue size reaching to around 90,000 or more. For this I have set the property nifi.queue.swap.threshold to 90000 . We also have a disk space of 200 GB. Despite having such a powerful configuration , we still get flow file repository failed to update. I understand that initially the JVM memory is uitilized for the flow file processing and if that gets overused , it spills over to disk space . Our disk space is also pretty high at 200 GB however we still keep on seeing this error. Any pointers or suggestion in this space will be of great help.

abhinav_joshi · ‎02-24-2019

Hi Rishabh , did you try shutting down the nifi instances and start them one at a time ?

abhinav_joshi · ‎02-21-2019

Got this fixed now 🙂 . Actually there is an extra line in the zookeeper.properties file which is right at the end and that line creates an issue . It just needs to be deleted and this will then work like a charm .

abhinav_joshi · ‎02-21-2019

Ok , we managed to get the answer to this. If Minifi for some reason isnt able to transmit data to the Nifi server , the minifi content repository starts getting filled up and this needs to be avoided. So , we need to add some space to the filesystem that points to the content repository as a best practice in production.

abhinav_joshi · ‎02-21-2019

Hi Rishabh , Have a look at https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/ This one is really good . I have followed this although I am stuck . Waiting for Pierre Villard to respond

abhinav_joshi · ‎02-21-2019

HI All , I have created 2 nifi instances on Google Cloud Platform. I now plan to bring them onto a cluster. However I am getting this error server.quorum.QuorumPeerConfig does not have the form host:port or host:port:port or host:port:port:type I have checked my zoo keeper properties file again and again but not sure whats the issue. My zoo keeper properties file is as follows . I am not sure as to why this issue is cropping up. My nifi servers are by the name nifi-server2 and nifi-server1 and ports are 2888 and 3888 . I have followed the documentation by Pierre Villard. server.1=nifi-server2:2888:3888 server.2=nifi-server1:2888:3888 # server.3=nifi-node3-hostname:2888:3888 Can someone please help me here.

Online	Offline
Last Visited	‎08-12-2021 05:31 PM

Member Since	‎03-26-2018 03:03 AM
Last Visited	‎08-12-2021 05:31 PM
Posts	110
Kudos received	10

Cloudera Community

Re: Apache Nifi Mysql Connectivity - Cannot creat...

Re: Nifi cluster CPU Utilization / RAM always pea...

Re: Flow file repository failed to update Errors -...

Re: Nifi Cluster Start up issue :- server.quorum....

Re: Minifi and Log Size

Re: Update Attribute processor Not working after u...

Re: Update Attribute processor Not working after u...

Update Attribute processor Not working after upgra...

Re: Flow file repository failed to update Errors -...

Flow file repository failed to update Errors - Don...

Re: Nifi Cluster Start up issue :- server.quorum....

Re: Nifi Cluster Start up issue :- server.quorum....

Re: Minifi and Log Size

Re: Nifi Cluster Start up issue :- server.quorum....

Nifi Cluster Start up issue :- server.quorum.Quor...