Hi, We have taken a look at MiNiFi, and the reason why we want to use NiFi still is because of the REST API that NiFi provides which we want to use to dynamically rewire the processors whenever needed without needing to halt all the processors in the graph.
>From what I understand of MiNiFi, this is not possible. Any changes to the processor graph will involve a restart. So if there are disconnected components of the processor graph, then they will be restarted unnecessarily. This can be avoided in NiFi. However, let me know if I am missing anything here. Thanks for the link though. I'll see if I can find anything there. Pushkar On Fri, Mar 3, 2017 at 3:32 PM, Andrew Psaltis <[email protected]> wrote: > Pushkar, > I just realized after sending the email, that I did not provide any > resources where you can learn more about MiNiFi outside of the Apache site. > Here are some resources that may make your experience a little smoother: > > Edge Intelligence with MiNiFi -- > https://hortonworks.com/webinar/edge-intelligence-iot-apache-minifi/ > Reading Sense HAT data - > https://community.hortonworks.com/articles/85984/using- > minifi-to-read-data-from-a-sense-hat-on-a-ra.html > NiFi on a Rasp. PI Best Practices - > https://community.hortonworks.com/articles/32605/running- > nifi-on-raspberry-pi-best-practices.html > -- this does not cover MiNiFi, thus it may have some pointers for solving > the current problem you are having. > > Hope that helps. > > On Fri, Mar 3, 2017 at 3:27 PM, Andrew Psaltis <[email protected]> > wrote: > > > Pushkar, > > While it certainly should and has been possible to run regular NiFi on a > > PI. Perhaps the best way forward is to actually use MiNiFi [1]. MiNiFi is > > available in as a C++ and Java agent and designed explicitly to run on > > devices. > > > > I'm sorry I could not be of more assistance with the actually config > > changes you may want to make, I am traveling at the present time and do > not > > have access to a PI. > > > > > > [1] https://nifi.apache.org/minifi/index.html > > > > Thanks, > > Andrew > > > > On Fri, Mar 3, 2017 at 3:21 PM, Pushkara R <[email protected]> > wrote: > > > >> Hi, > >> > >> I'm getting NiFi to run on a raspberry pi. the bootstrap takes a very > long > >> time. But at the end, the port doesn't open because of a jetty issue and > >> NiFi shuts down. I've pasted the exception below. > >> > >> A quick look at stackoverflow tells me I need to insrease the timeout > >> value > >> to go around this. But I do not know how to change it, I'm not sure if > it > >> is picking it up at runtime or not. > >> > >> Any assistance would be helpful. > >> > >> Thanks > >> Pushkar > >> > >> PS : the stacktrace > >> > >> java.lang.Exception: Timeout scanning annotations > >> at > >> org.eclipse.jetty.annotations.AnnotationConfiguration.scanFo > >> rAnnotations(AnnotationConfiguration.java:575) > >> ~[jetty-annotations-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.annotations.AnnotationConfiguration.config > >> ure(AnnotationConfiguration.java:447) > >> ~[jetty-annotations-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.webapp.WebAppContext.configure( > WebAppContext.java:494) > >> ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppCo > >> ntext.java:1361) > >> ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.server.handler.ContextHandler.doStart( > >> ContextHandler.java:772) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.servlet.ServletContextHandler.doStart(Serv > >> letContextHandler.java:262) > >> ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:520) > >> ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.AbstractLifeCycle.start( > >> AbstractLifeCycle.java:68) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.start( > >> ContainerLifeCycle.java:132) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart( > >> ContainerLifeCycle.java:114) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.server.handler.AbstractHandler.doStart( > >> AbstractHandler.java:61) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.AbstractLifeCycle.start( > >> AbstractLifeCycle.java:68) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.start( > >> ContainerLifeCycle.java:132) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart( > >> ContainerLifeCycle.java:106) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.server.handler.AbstractHandler.doStart( > >> AbstractHandler.java:61) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart( > >> GzipHandler.java:231) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.AbstractLifeCycle.start( > >> AbstractLifeCycle.java:68) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.start( > >> ContainerLifeCycle.java:132) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at org.eclipse.jetty.server.Server.start(Server.java:411) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart( > >> ContainerLifeCycle.java:106) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.server.handler.AbstractHandler.doStart( > >> AbstractHandler.java:61) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at org.eclipse.jetty.server.Server.doStart(Server.java:378) > >> ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.eclipse.jetty.util.component.AbstractLifeCycle.start( > >> AbstractLifeCycle.java:68) > >> ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517] > >> at > >> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:675) > >> ~[nifi-jetty-1.1.2.jar:1.1.2] > >> at org.apache.nifi.NiFi.<init>(NiFi.java:156) > >> [nifi-runtime-1.1.2.jar:1.1.2] > >> at org.apache.nifi.NiFi.main(NiFi.java:262) > >> [nifi-runtime-1.1.2.jar:1.1.2] > >> > > > > > > > > -- > > Thanks, > > Andrew > > > > Subscribe to my book: Streaming Data <http://manning.com/psaltis> > > <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306> > > twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata> > > > > > > -- > Thanks, > Andrew > > Subscribe to my book: Streaming Data <http://manning.com/psaltis> > <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306> > twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata> >
