Hi,
also the Toolkit is available in the NiFi image as well, preconfigured to
be used against the locally running instance. Example:
docker run -d apache/nifi:1.8.0
389997393ef93496b875277a3667bca483c8ccee0f99513c61d7d447042df09a
docker exec
, Oct 25, 2018 at 3:07 PM Stephen Greszczyszyn
wrote:
>
>
> On Thu, 25 Oct 2018 at 12:50, Peter Wilcsinszky <
> peterwilcsins...@gmail.com> wrote:
>
> But even with 1.8 I'll need to declare the host mount directory somehow
> via docker-compose, as how will the built doc
opt/nifi/flowfile_repository
> -
> /data/nifi/content_repository:/opt/nifi/content_repository
> -
> /data/nifi/provenance_repository:/opt/nifi/provenance_repository
>
> ports:
> - 8080:8080
> - 8443:8443
>
Hi Stephen,
I don't recommend mounting /opt/nifi directly as it will copy all the NiFi
binaries over to the volume as well, which is unnecessary I beleive. The
latest dockerfile that will be used to build the docker image for the
upcoming release already declares volumes that I recommend to
...
Peter
On Wed, Oct 24, 2018 at 9:40 PM a.toy wrote:
> Peter Wilcsinszky wrote
> > what is your service yaml exactly? how do you create the pods is it a
> > statefulset?
>
> My sts.yaml and service.yaml files are pretty straight-forward:
>
> */sts.yaml:/*
>
Hi Adam,
On Wed, Oct 24, 2018 at 8:29 PM a.toy wrote:
> Trying to get NiFi working in Openshift (as Docker containers) but
> struggling
> with the networking. For those who don't know Openshift well, the hostname
> of the container is NOT routable from other containers. The 'proper' way to
>
Hi Ara,
I can see that the Toolkit version is 1.7.1 but what versions of NiFi and
NiFi Registry are you using?
Can you perform an ssldump [1] on the Toolkit or the Registry side to see
the TLS handshake error (supposing that is the issue) more closely?
[1]
Hey,
I can't tell about the original intent and motivations, but this is the
Jira that introduced this check [1].
What I can tell is mutual TLS is not the only option to authenticate
against NiFi. You can set up LDAP for example to authenticate the client
and in that case MITM is possible I
containerPort: 8080
>
> - name: cluster
>
>containerPort: 8082
>
> volumeMounts:
>
> - name: repositories
>
> mountPath: /mnt
>
> volumeClaimTemplates:
>
> - metadata:
>
> name: re
I beleive the problem is that you don't use PersistentVolumeClaims with
your statefulset. Do you have a specific reason not using persistent
volumes for your data and/or mutable config (authorizations.xml, users.xml,
flow.xml.gz)?
On Sun, Sep 23, 2018 at 7:25 PM Peter Wilcsinszky <
peterwilcs
r.connect.string=qazknifi.com:2181|"
> /opt/nifi/nifi-1.7.0/conf/nifi.properties;
> sed -i -e
> "s|^nifi.zookeeper.root.node=.*$|nifi.zookeeper.root.node=/test|"
> /opt/nifi/nifi-1.7.0/conf/nifi.properties;
> sed -i -e "s|^java.arg.2=.*$|
only issue as I said is if we restart any undeying node we extra node
> and old nodes does not get deleted.
>
With a statefulset you wouldnt have issues with that and you would have
stable persistent volumes as well.
>
> Regards,
> Varun
>
> --
> *F
Hi,
I haven't done extensive research in this area but ran through the articles
and also found another one [1]. From what I understand
UseCGroupMemoryLimitForHeap is just the dynamic version of setting memory
limits manually using Xmx and Xms which is currently done by the NiFi start
script
13 matches
Mail list logo
