@Sivagopal   Check out this post for a similar scenario.  It includes a solution:   https://community.cloudera.com/t5/Support-Questions/Nifi-1-16-fails-to-start-with-Decryption-exception/m-p/358190     ... View more

@fahed What you see with the CDP Public Cloud Data Hubs using GCS (or object store) is a modernization of the platform around object storage.  This removes differences across aws, azure, and on-prem (when Ozone is used).    It is a change by customer demand so that workloads are able to be built and deployed with minimal changes from on prem to cloud or cloud to cloud.   Unfortunately that creates a difference you describe above, but those are risks we are willing to take ourselves in favor of modern data architecture.   If you are looking for performance, you should take a look at some of the newer options for databases: impala and kudu (this one uses local disk).  Also we have Iceberg coming into this space too. ... View more

@Pierro6AS  First thing you should do is increase the size of the message queue.  The default size is quite low (10,000 records and 1gb).   It is possible to see this error if the flowfiles have been in the queue for too long.   It is also possible to see this error if the file system has other usage outside of nifi.  For best performance nifi's backing folder structure (content/flowfile repository) should be dedicated disks that are larger than the demand of the flow (especially during heavy unexpected volume).     You can find more about this in these posts: https://community.cloudera.com/t5/Support-Questions/Unable-to-write-flowfile-content-to-content-repository/td-p/346984 https://community.cloudera.com/t5/Support-Questions/Problem-with-Merge-Content-Processor-after-switch-to-v-1-16/m-p/346096/highlight/true#M234750   ... View more

@kishan1 In order to restart a specific processor group you will need to use some command line magic against the Nifi API.  For example, this could be done by using a command to stop the processor group, then the restart nifi command, then start processor group.  You can certainly be creative in how you handle that approache once you have experimented with the API.   https://nifi.apache.org/docs/nifi-docs/rest-api/index.html     ... View more

@merlioncurry   Lacking a bit of deatils, so making some assumptions that you used an Ambari UI to upload to HDFS.  So those files are going to be in hdfs://users/maria_dev,  not on the actual machine location for the same users.  You will need use hdfs commands to view them.  If they do not work, then the path you uploaded may be different.   From the sandbox prompt:   hdfs dfs -ls /users/ hdfs dfs -ls /users/maria_dev   ... View more

@fahed The HDFS Service inside of the DataLake is supporting of the environment, and its services. For example:  Atlas. Ranger, Solr, Hbase.  It's size, is based on the environment scale.   You are correct in the assumption that your end user HDFS Service is part of Data Hubs deployed around the environment.  You should not try to use the environment's HDFS Service for applications and workloads that would be part of deeper Data Hubs. ... View more

@Iwantkakao  There are 2 things i see right off bat:   Tue Jan 31 19:47:13 UTC 2023 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. ^^ consider the recommendation:   useSSL=false in your sqoop command.   23/01/31 19:47:14 ERROR manager.SqlManager: Error executing statement: java.sql.SQLException: Access denied for user ''@'localhost' (using password: NO) java.sql.SQLException: Access denied for user ''@'localhost' (using password: NO) ^^ this error is saying that your user does not have access to mysql.  You are going to need to provide a specific user, password, and host, with permissions and grants accordingly.   If your user is root, add the username and password to the command.       Last but not least, sqoop project is now "in the attic" which means the project is no longer actively getting support and developement from the open source community.   I recommend that you learn other techniques to complete the same outcome.     ... View more

@samrathal Per the docs you need to provide the ID:   Request consumes: */*   Name Location Type Description id path string The connection id. flowfile-uuid path string The flowfile uuid. clusterNodeId query string The id of the node where the content exists if clustered. You should be getting that ID from the previous get call ( Gets a FlowFile from a Connection ) within the response is an object:  FlowFileEntity   Inside is the  "clusterNodeId"  corresponding to which node that flowfile exists on.   { "flowFile": { "uri": "value" , "uuid": "value" , "filename": "value" , "position": 0 , "size": 0 , "queuedDuration": 0 , "lineageDuration": 0 , "penaltyExpiresIn": 0 , "clusterNodeId": "value" , "clusterNodeAddress": "value" , "attributes": { "name": "value" } , "contentClaimSection": "value" , "contentClaimContainer": "value" , "contentClaimIdentifier": "value" , "contentClaimOffset": 0 , "contentClaimFileSize": "value" , "contentClaimFileSizeBytes": 0 , "penalized": true } }  Those details are exposed in the nifi api doc, just be sure to click into the entity. ... View more