Member since
08-08-2024
111
Posts
28
Kudos Received
13
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 91 | 06-12-2026 07:16 AM | |
| 359 | 05-26-2026 11:44 AM | |
| 320 | 05-26-2026 09:56 AM | |
| 487 | 04-15-2026 11:56 AM | |
| 1197 | 04-07-2026 02:00 PM |
06-15-2026
11:27 AM
Hello @intersoldi, Thanks for being part of our community. This could be an issue related to some threads blocked. Do you see anything on the YARN application log? On the Spark Event Log, does it always hang on the same task? Another thing you can try is to get jstacks and review them to see if they are hanging on any specific point or step, for example, a connection or thread.
... View more
06-12-2026
07:16 AM
Hello @Seaport, Thanks for reaching Cloudera Community. Unfortunately, there is no option to use Airflow on base cluster. The only possible way to use it is with Data Services, in this case CDE.
... View more
05-29-2026
05:59 AM
Hello @LaurisG_, Glad to hear that. Have a great weekend too,
... View more
05-27-2026
01:18 PM
Hello @AlokKumar, The log used the Processor or Group ID, not the name. This is because you can have multiple processor for the same one, but the ID is always unique. On this example, the ID is: 3be575b5-019e-1000-0000-00002f93e650 The user is also reported between the [], in my case, is vafs: 2026-05-26 18:29:51,455 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
... View more
05-26-2026
11:44 AM
Hello @LaurisG_, Hope you are doing fine. I think this one is also related to the CM version you have, as mentioned on: https://community.cloudera.com/t5/Support-Questions/Ranger-UserSync-and-RMS-fails-after-upgrade-7-1-9-7-3-2-0-GA/td-p/414110 As this is unsupported it may send wrong settings to the services. Can you try upgrading the CM and see if the Atlas service starts properly?
... View more
05-26-2026
11:41 AM
Hello @AlokKumar, Thanks for being part of the community. Yes, that is possible. You should be able to search on the nifi-user.log for entries. You can either filter them by user or by processor IDs. For example, I did some starts and stops for this processor. By checking the log using the ID, I found this: 2026-05-26 18:29:40,582 INFO [NiFi Web Server-36464] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:40,582 INFO [NiFi Web Server-36464] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:40,597 INFO [NiFi Web Server-33000] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:40,598 INFO [NiFi Web Server-33000] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
...
2026-05-26 18:29:51,454 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:51,455 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:51,465 INFO [NiFi Web Server-36510] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status
2026-05-26 18:29:51,465 INFO [NiFi Web Server-36510] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/processors/3be575b5-019e-1000-0000-00002f93e650/run-status Also, by checking the ID for a proccessor group I see the following: 2026-05-26 18:31:40,166 INFO [NiFi Web Server-36460] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de
2026-05-26 18:31:40,167 INFO [NiFi Web Server-36460] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de
2026-05-26 18:31:40,187 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.129.x.x [<vafs><CN=node1.cfm-vafs.cloudera.com, ST=CA, C=US>] PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de
2026-05-26 18:31:40,188 INFO [NiFi Web Server-36459] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [vafs] 10.129.x.x PUT https://node1.cfm-vafs.cloudera.com:8443/nifi-api/process-groups/658e5692-019e-1000-ffff-ffff8f55b0de This should give you the information you want.
... View more
05-26-2026
09:56 AM
1 Kudo
Hello @LaurisG_, Thanks for being part of our community. I was reading through the issue and found a similar issue reported before. The issue was an unsupported Cloudera Manager used for the Runtime. And in your scenario, this is happening too. You mentioned you have Cloudera Manager 7.11.3, but this version does not support Cloudera Runtime 7.3.2. That could cause the issue you're seeing. You should be using Cloudera Manager 7.13.2, as that is the supported version for your Runtime. https://docs.cloudera.com/cdp-private-cloud-base/7.3.2/cdp-private-cloud-base-installation/topics/cm-cdh-compatibility.html https://supportmatrix.cloudera.com/ Try upgrading the CM and then retry the Role start.
... View more
05-12-2026
03:06 PM
Hello @nisaar, sftp CLI and PutSFTP can internally work differently. Have you check nifi-app.log from the NiFi nodes to review the error? If so, can you share here the message to take a look.
... View more
05-06-2026
02:07 PM
Hello @Dagonvlg, The best option should be on NiFi UI, in that way you can execute it as stateless: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-stateless-processor-nar/1.28.0/org.apache.nifi.processors.stateless.ExecuteStateless/index.html
... View more
04-24-2026
11:57 AM
1 Kudo
Hello @Dagonvlg, As far as I know, NiFi 2 does not have a stateless mode to the entire service. That was removed. But what it offers is an stateless engine. You can configure it at Processor Group level: https://nifi.apache.org/nifi-docs/user-guide.html#stateless-execution-engine
... View more