Thank you for your email. Looking at the zookeeper docs, with 3.5.0 it
looks like the format may have changed to support the dynamic
configuration. It may seem that zookeeper is sending back a format that
NiFi isn't expecting??? I.e the :participant
https://zookeeper.apache.org/doc/r3.5.6/zookeepe
In my memory,
zookeepr 3.5.6 needs the new form of zookeeper string such as
server.1=0.0.0.0:2888:3888;2181
where the ip is yours.
Hope this help you.
2020년 2월 13일 (목) 오전 1:55, dan young 님이 작성:
> Sorry Joe,
>
> Yes, I'll file a JIRA...here's the email again
>
> We're seeing the followin
You could use MiNiFi agents on each external resource to consume data in a
siloed manner and transmit it to a central NiFi instance over Site-to-site
protocol. This would allow each producer of data to remain isolated (either
physically disconnected or each using a distinct OS user for ACL with
Sorry Joe,
Yes, I'll file a JIRA...here's the email again
We're seeing the following messages in nifi logs on our cluster nodes.
Using
Nifi 1.11.1 and zookeeper (not embedded) version 3.5.6
Functionality seems not to be impacted, but wondering if there's something
else
going on or the versio
Dan,
Not sure what others see but for me your email cuts off in the middle of a
line.
You might want to file a JIRA with your observation/logs.
Thanks
On Wed, Feb 12, 2020 at 11:46 AM dan young wrote:
> Hello,
>
> We're seeing the following messages in nifi logs on our cluster nodes. Using
>
Hello,
We're seeing the following messages in nifi logs on our cluster nodes. Using
Nifi 1.11.1 and zookeeper (not embedded) version 3.5.6
Functionality seems not to be impacted, but wondering if there's something else
going on or the version of zookeeper we're using is causing this.
2020-02-12
Hi guys,
I'm having this situation inside my company projects. We are using NiFi as
DataFlow platform and there are multiple projects.
Every project has files on shared disk/folder from which one Nifi
instance(standalone instance) is reading data.
NiFi instance service is running under one generic
For the sake of testing I have just been running everything as root.
Permissions look good to me.
[root@wvllab-lnx-nifi conf]# ls -la
total 116
drwxr-xr-x 3 root root 4096 Feb 12 00:13 .
drwxr-xr-x 16 root root 328 Feb 11 23:36 ..
drwxr-xr-x 2 root root86 Feb 12 00:02 archive
-rw-r--r--
Most of your pain points with performance will be either CPU or disk I/O
unless you happen to have a particularly memory-intensive flow (most
aren't). I'd start with a heap of about 4GB of RAM/node and scale up from
there as needed while testing. Odds are pretty good that you'll find that
adding co
Hello,
It looks like basically the same error you had for authorizers.xml,
but now for login-identity-providers.xml.
It is saying the file does not exist at
/apps/nifi-test/./conf/login-identity-providers.xml
Can you verify the file exists and it is readable by whatever OS user
NiFi is running a
Hi All,
We use Digital Ocean, just wish to check with the community if we should
go for general purpose machines or memory-intensive machines for our NiFi
cluster?
Regards
Anurag
11 matches
Mail list logo
