Re: Unable to access flowfile content

de， just delete the flow.xml.gz file and > restart the node, the flow file will be synced from the other two nodes. > > Regards, > Lei > > > > wangl...@geekplus.com.cn > > From: Purushotham Pushpavanthar > Date: 2019-12-19 17:05 > To: dev > Subject: Unable to access f

Unable to access flowfile content

Hi, We've have 3 node production cluster running seamlessly for almost 8 month with manageable ups and downs. However, yesterday we ran into an issue in one of the processors due to which CPU shot up and node went down. On restart, the contents of few enqueued flowfiles went missing all of sudden

Implementation of FilesystemComponentStatusRepository

Hi, Right now we only have volatile implementation of ComponentStatusRepository which serves status report of each component. Though we have reporting tasks like AmbariReportingTask, PrometheusReportingTasks which push metrics to external persistent systems, NiFi's Component Status History serves

NiFi - Cluster crashes while running CaptureChangeMySQL for CDC

Hi, I've been trying to run CDC in 3 node NiFi (ver : 1.9.2) cluster similar to the what is illustrated here . However, I've been facing below issue because of scale. When I start the

Re: Unable to modify flow when one of the nodes in a cluster is disconnected

hanges and join the cluster. But if you have > changed a processor's properties, for > instance, this will result in the node failing to join the cluster and > indicating that the local flow differs from the cluster's flow. > > > On Jun 29, 2019, at 2:53 PM, Purushotham Pushpavanthar

Re: Unable to modify flow when one of the nodes in a cluster is disconnected

ere are > definitely > areas where we could improve, but it's just not been taken on yet by > anyone in the community. > > Thanks > -Mark > > > On Jun 27, 2019, at 3:37 AM, Purushotham Pushpavanthar < > pushpavant...@gmail.com<mailto:pushpavant...@gmail.com>> w

Unable to modify flow when one of the nodes in a cluster is disconnected

Hi, I'm having a 3 nodes( ver 1.9.2) cluster running in production. As infra is unreliable due to various factors, our nodes go down often. We don't have distinction between dev and prod cluster. We modify, deploy, test in the same cluster. However, when one of the node goes down NiFi restricts