Member since
03-10-2017
157
Posts
79
Kudos Received
32
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
342 | 08-12-2024 08:42 AM | |
883 | 05-30-2024 04:11 AM | |
1273 | 05-29-2024 06:58 AM | |
785 | 05-16-2024 05:05 AM | |
644 | 04-23-2024 01:46 AM |
08-12-2024
08:42 AM
The details you see in UI other the actual content is loaded in memory and kept stored under flow file repository and content is in content repostoriru If I just take the example of flow file details, it has content that is located in Section 1 means Directory 1 under the content repo with an identifier number. So the question is after every restart does your content repository location persist?
... View more
08-12-2024
08:29 AM
From the logs snipped, it appears that the NiFi node does not have all the permissions, to get more clarity it would be nice if you could add the error you see in NiFi UI related to permissions. Thank you
... View more
08-12-2024
08:17 AM
1 Kudo
If I understand correctly, Service NiFi works fine but from the Cloudera Manager things do not look promising this has to do with how CM monitors the NiFI service I would start to at the logs directory under the NiFi processor directory on each host where niFi is running and look for file connectionMetricOutput.log NNNNNNNN-nifi-NIFI_NODE/logs/connectionMetricOutput.log On each Node where NiFi service is running, CM agent invokes nifi cli command get-nodes to get the health status of each node. bin/cli.sh nifi get-nodes If you find get-nodes command is not completing, you may want to further file a support case with us to look in detail. I hope this helps. Thank you
... View more
06-03-2024
04:13 AM
2 Kudos
NiFi Registry is a single-point service, Not meant to sync flow versioning with multiple NiFi Registry. Not sure how this is set up at your end you can provide an overview of your Architecture between NiFi and NiFi Registry and Git so I can understand further. Thank you
... View more
06-03-2024
02:39 AM
@Naveen_Sagar, can you provide a complete error stack to understand the cause behind the connection reset? along with processor property details
... View more
05-30-2024
04:11 AM
2 Kudos
This is not possible since Scheduling Strategy can not be set dynamically or via any attribute (flow or variable ) Thank You
... View more
05-29-2024
06:58 AM
1 Kudo
The following command I have tested and found working, make sure you are passing the right token as sometimes you may end up using extra information in the token curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer <TOKEN>" -d '{"state": "RUNNING", "id": "processor-id", "revision": {"version": versionNumber, "clientId": "clidntIDstring"}}' -k --negotiate "https://hostname:8443/nifi-api/processors/<ID>/run-status" Also please make sure the user has permission to WRITE permission on components
... View more
05-28-2024
02:02 AM
3 Kudos
Log rotation settings have No/Driect impact on NiFi data flow processing performance. It is just that there should be enough space available on the file system to store the log files. Thank you
... View more
05-16-2024
05:05 AM
2 Kudos
You might be looking at the most recent version of the document. Include all violation is added from Apache NiFi 1.25 version https://issues.apache.org/jira/browse/NIFI-12593. I hope this helps. Thank you
... View more
04-23-2024
01:46 AM
1 Kudo
Not possible, there is a reason for that if we allow to add a property to set an initial offset, every time that processor was stopped and started we would again start at that configured offset, with console consumer, you only pass the initial offset on the first execution then subsequent executions use the last stored offset in Kafka, which is not the case here with the processor. Thus only two options are "earliest" or "latest". Thank you
... View more