@akylai ,   The Cloudera Quickstart docker image contains a very old version from CDH and is no longer supported. If you want to try the Cloudera Data Platform (CDP), I'd recommend you use the Cloudera Private Cloud trial: https://www.cloudera.com/downloads/cdp-private-cloud-trial.html   Regards, André ... View more

@CloudNaive ,   It seems that the "Message Key Field" property doesn't work with a nested structure. This property must refer to a top level field of the record that contains the key value. In the example below I used UpdateRecord to create a top level field called "id" and update it with the value of "metadata.aggregateId". Them, on the PublishKafkaRecord I was able to use the "id" field as the Kafka message key.   Cheers, André   ... View more

@templarian ,   Are there any messages in nifi-app.log related to the processor around the time of the crash? It might help enabling DEBUG for NiFi and the processor and trying to reproduce the problem. Please share the debug logs if you manage to get them.   André ... View more

This may be related to insufficient resources on your environment. Could you share a screenshot of the Cluster Metrics table you can find under Admin > Overview? On that same page you can also find a link to a Grafana Dashboard where you can check the resource utilisation at various levels.   Regards, André ... View more

Also, running the command "cdsw logs" as root on the CDSW host will collect logs from the CDSW containers, which you can use to troubleshoot.   ... View more

Have you trying stopping and starting the model? Or redeploying it? ... View more

@NajAb8 / @seanbenner ,   Do you see anything in the "Monitoring" tab?   Cheers, André ... View more

Hi, @Suriyakanth ,   Are the FTP servers in the FetchFTP and PutFTP processors the same or are they different? You are using CDP Public Cloud and to access the FTP server you must ensure that your NiFi nodes have network connectivity to it by configuring your cloud security groups correctly.   I imagine you have an active Cloudera subscription, right? Do you have a support case open? If so, could you please PM me the case number?   Cheers, André ... View more

Hi, @hamsterrrrr ,   Those events represent the point-in-time occurrence when the alert was thrown. They don't tell you the current issues with the cluster, which is what you see in the UI. I don't think the REST API has an endpoint that gives you that list directly, but it's pretty easy to find out.   In the results of the /clusters/{cluster}/services endpoint, look for services with the status = BAD or health checks with summary = BAD. For example: { "items": [ { "name": "impala", "type": "IMPALA", "healthSummary": "BAD", <<--- this "healthChecks": [ ... { "name": "IMPALA_IMPALADS_HEALTHY", "summary": "BAD", <<--- or this "suppressed": false }, ... ], ... } ] }   Cheers, André ... View more