Does anyone know if there is a way to use impala over TLS that doesn't require you putting passwords in cleartext? (CFM 2.0.4) ... View more

Cloudera Flow Management (CFM) 2.0.4.3 1.11.4.2.0.4.3-1 built 01/06/2021 23:14:00 CST Tagged nifi-1.11.4-RC1 ... View more

Okay then, How about this: Does anyone know what path it's checking on the name node when I see this?   Failed to retrieve/store URL: https://<hostname>:<port>/cmf/parcel/download/CDH-6.3.3-1.cdh6.3.3.p0.1796617-el7.parcel.torrent -> /opt/cloudera/parcel-cache/CDH-6.3.3-1.cdh6.3.3.p0.1796617-el7.parcel.torrent HTTP Error 404: Not Found Originally looking in /opt/cloudera/parcel-cache/ which has the file, noticed that /opt/cloudera/parcel-repo/ does not have the file ... View more

Thanks for taking time to explain, trying to untangle the version numbers etc. are a new challenge. 🙂 I guess I was confused since our cloudera runtime still says cdh7.1.5... I need to get with one of my coworkers on this, because my access still won't let me create a support case. 😞 (which is why I am here. 🙂 ) ... View more

Hmm, don't remember seeing the 'private cloud' nomenclature before. our new version might work (Cloudera Enterprise 7.2.4) Cloudera Flow Management (CFM) 2.0.4.3 1.11.4.2.0.4.3-1 built 01/06/2021 23:14:00 CST Tagged nifi-1.11.4-RC1 But most of our stuff (Cloudera Enterprise 6.3.3) might be limited to the 1.1 branch. Cloudera Flow Management (CFM) 1.1.0.0 1.11.4.1.1.0.0-119 built 04/24/2020 19:39:59 CDT Tagged nifi-1.11.1-RC1   ... View more

Yes, that screenshot looks like what I get when logged in via a user account. After you add a parameter/value and hit apply, one green check then red X's the rest of the way down. I had the AD folks create me a test user and have been trying all sorts of combinations of permissions, and they all have resulted in the same error. Mostly just parameter context and controller related permissions, the user group has permissions to the PC in question, and I even gave the group permission to create new PC, but they still couldn't create a parameter. We installed cfm 1.1.0.0 on one cluster, and 2.0.4.3 on another, both indicate NiFi 1.11.4, I will have to look into patch/upgrade paths, these are both new installs, different versions of cloudera. ... View more

As it stands now, in NiFi 1.11.4, it seems that PGs do not inherit the context of their parent. 😕   It would certainly be nice if they added actual scoping rules and inheritance, rather then the all or nothing we have now. I don't see a good way to copy them either. 😞 So even if you wanted to have several sets of parameters with mostly the same values, and a few different, you have to do it the hard way. Everything else seems to work by (optionally in some cases) inheriting from the parent, so it is puzzling that parameters do not. ... View more

The full info from the app log is: 2021-05-17 14:57:12,166 INFO org.apache.nifi.web.api.ParameterContextResource: Stopping 0 Processors in order to update Parameter Context 2021-05-17 14:57:12,173 ERROR org.apache.nifi.web.api.ParameterContextResource: Failed to update Parameter Context org.apache.nifi.web.util.LifecycleManagementException: Failed while waiting for components to transition to state of STOPPED at org.apache.nifi.web.util.ClusterReplicationComponentLifecycle.scheduleComponents(ClusterReplicationComponentLifecycle.java:133) at org.apache.nifi.web.api.ParameterContextResource.stopProcessors(ParameterContextResource.java:960) at org.apache.nifi.web.api.ParameterContextResource.updateParameterContext(ParameterContextResource.java:852) at org.apache.nifi.web.api.ParameterContextResource.lambda$submitUpdateRequest$17(ParameterContextResource.java:804) at org.apache.nifi.web.api.concurrent.AsyncRequestManager$2.run(AsyncRequestManager.java:117) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)   ... View more

I said in the question, there are no other parameters, until I created one, and there are no components referencing any parameters, because I just created the context. There aren't any other contexts, no components are using parameters, because it won't allow the uses to create them. Since I saw a question with the same version and error code, was kind of hoping someone had a "Oh you forgot to << missing step >> when ..." type answer. 🙂 ... View more

I have a user getting this error as well, not finding much about it. These are brand new contexts, trying to create a first parameter. It gives me (administrator) no problems, but the user is apparently missing a policy, or something (bug?) ... View more