RE: HandleHttpRequest - Failed to receive content from HTTP Request

Looking for similar issues in google these ones seem to be close: https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-handlehttprequest-response-issue/m-p/199086 http://apache-nifi-users-list.2361937.n4.nabble.com/HandleHttpRequest-failing-td1062.html I'm pretty sure I'm terminating

Policy storage in Nifi runner and Kubernetes

Hi all I'm running my Nifi node in Kubernetes. For that, the /opt/nifi/nifi-current/conf folder is made writable by an init container prior to starting the runner. All other interesting folders (the *_repository ones) are stored on a read-write-once volume. Each time the pod is restarted, the

CaptureChangeMySQL lost binlog position info when restarted or master slave swiched

The CaptureChangeMySQL can only run on primary node. When the primary node is switched, the previous binlog position info not work. Usually the processor will consume from the earlist binlog postion. I am using zookeeper state-management. Any insight on this? Thanks, Lei

Memory issues when using NiFi to replicate mysql database with CaptureChangeMySQL

Usnig CaptureChangeMySQL do parse binlog, then do some transformation and finally put the result to another database. And at the same time put binlog msg to Message Queue. Some controller services are used, HortonworksSchemaRegistry, DistributedMapCacheServer, JSONTreeReader，JSONTreeWriter,

Re: Policy storage in Nifi runner and Kubernetes

ok, it appear my nifi node doesn't start an embedded zookeeper server. Can it be related ? Le 30/09/2019 à 09:59, Nicolas Delsaux a écrit : Hi all I'm running my Nifi node in Kubernetes. For that, the /opt/nifi/nifi-current/conf folder is made writable by an init container prior to starting