Re: Proposing NiFi-Fn

Hi David! That is a nice one as well! I can see you have a custom NiFi image, but can not track back to the Dockerfile, could you point to where we can find it? (I understand it's marginal, just curious) Cheers, Peter On Tue, Feb 12, 2019 at 8:04 PM David Kegley wrote: > Sam, > > This is

Re: Can nifi cluster which enabled SSL be scaled without reboot in kubernetes

Hi Fugui! There is no need to restart the nodes. You should use a properly filled authorizers.xml for the initial cluster nodes only. Then as you add new nodes you should use an authorizers.xml that is "empty" meaning it has no nodes and users in it, neither the initial admin defined in the

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Hi, are your hosts registered in LDAP properly? If you don't want them to come from LDAP then they should come from the file-user-group-provider as initial user identities in addition to your "Initial User Identity 1". Peter On Tue, Sep 18, 2018 at 11:54 AM nifi-san wrote: > Hello, > > We are

Re: Question about nifi-env.sh

Hi Lars! The idea you proposed - to set only what has not been set already - makes sense, however it may cause unexpected side effects in deployments where there are environment variables hidden by nifi-env.sh. This is theoretical, but I can imagine situations where operators tried to set

Re: [PROPOSAL] Reference Utility Script to help automate some of RC validation in Release Process

Hey Otto, I would like to try it and give feedback, I forgot to do this last time. On Mon, Aug 13, 2018 at 4:13 PM Otto Fowler wrote: > Does anyone have comment as to if they would be interested? I based the > script on another committer’s personal script, and we do use a script like > that >

Re: Version-Agnostic Paths in Docker?

aving said all that, certainly in favor of the path suggested, it makes > sense and is a nice and easy usability win. I would be sure to keep the > versioned approach for those folks who prefer that convention and then > additionally add a latest symlink. > > On Tue, Jul 31, 2018 a

Re: Version-Agnostic Paths in Docker?

Hi, I was wondering about this too. We have the option to add a symlink which you just mentioned and I can do that if there are no argument against. Also you can use the env var, when you do things through scripting: docker run --rm -ti --entrypoint bash apache/nifi:1.7.0 -c "echo \$NIFI_HOME"

Re: [DISCUSS] Tar + Gzip vs. Zip

/2921 Cheers, Peter On Fri, Jun 29, 2018 at 1:41 PM Peter Wilcsinszky < peterwilcsins...@gmail.com> wrote: > Yes, I mean with this (multistage build) we cannot get rid of the two > separate modules (maven and dockerhub) but we can get rid of the ADD > instruction which I think

Re: SSLPeerUnverifiedException Hostname "xyz" not verified

On Thu, Jul 19, 2018 at 12:38 AM Andy LoPresto wrote: > Hi Jon, > > There are automatable, scalable, and non-restart-required ways to > horizontally scale a secure cluster without requiring wildcard > certificates. I should collect the various instructions / notes together > into an article and

Re: [VOTE] Release Apache NiFi 1.7.1

+1 However I can't see the release tag "nifi-1.7.1-RC1". curl -s https://github.com/apache/nifi/tree/nifi-1.7.1-RC1 -w '%{http_code}\n' -o /dev/null 404 vs: curl -s https://github.com/apache/nifi/tree/nifi-1.7.0-RC1 -w '%{http_code}\n' -o /dev/null 200 Is it really missing or will be tagged

Re: [DISCUSS] Tar + Gzip vs. Zip

from them to use > in a new image. > > Thanks! > --aldrin > > On Fri, Jun 29, 2018 at 7:11 AM Peter Wilcsinszky < > peterwilcsins...@gmail.com> wrote: > > > Hi, > > > > I wrote about a different solution for which I implemented a PoC for in > >

Re: [DISCUSS] Tar + Gzip vs. Zip

Hi, I wrote about a different solution for which I implemented a PoC for in https://lists.apache.org/thread.html/6122674030b8f99a63d586dcdbdaf6b31841572aed63fcc9dcfb5eea@%3Cdev.nifi.apache.org%3E but multistage build could be a better option and I'm happy to create an issue and fix it for the

Re: Question on Docker module

temporary and as more people start to use it, it will converge to a fully multiplatform solution. Until then the dockermaven modul can stay of course to be available for legacy usage. Any feedback would be appreciated! Cheers, Peter On Thu, Jun 7, 2018 at 4:25 PM Peter Wilcsinszky wrote: >

Re: Question on Docker module

Hi, Disclaimer: I've been working with the nifi-docker module for only a couple of weeks now so I'm relatively new to this. Unfortunately there's no way I'm aware of right now using a pure Dockerfile to implement a build time switch for cases like this where you have a a) locally built binary b)

Re: Issue securing nifi with ca-server.

Hey Henk! Could you make any progress remote debugging your issue? Although not guaranteed to help, you may try and use strace to look into what's happening on the syscall level. For example I've ran this command after starting the server: strace -fp -s 100 2>&1 | grep -v clock_gettime | grep

Re: Issue securing nifi with ca-server.

Hey Henk! On Tue, Jun 5, 2018 at 2:34 AM, Henk Reder wrote: > Hello! > > My names Henk. I'm a web developer working on getting a nifi instance setup > for some integrations. > > Long story short, I setup this nifi deployment configuration back when > 1.5.0 was the latest version. Now that its

Re: Nifi Clustering not working

Jonathan, I think the issue is with how you apply the overrides in the properties file. I've removed the trailing comments from the overriden lines and it seems to be working. Peter On Fri, Apr 20, 2018 at 11:01 AM, Peter Wilcsinszky < peterwilcsins...@gmail.com> wrote: > Hi, > &

Re: Nifi Clustering not working

Hi, I've tested your statefulset and it seems it doesn't even try to connect to zookeeper to form a cluster, although the config looks good. I'm still new to this, but will dig deeper later. Peter On Tue, Apr 17, 2018 at 6:55 PM, Jonathan Kosgei wrote: > Thank you