Hello @Ellengogo    I am not able to find the exact Case reference as this Post is few months old. Typically, such issues are caused by Resource Constraint, wherein the Engine Pod (Created when a Workbench Session is started) gets terminated owing to Resource Constraint. If the issue is persistent, a Support Case would be ideal as we require the review of the Kubernetes Output pertaining to the Engine Pod along with Resource Profile & other related artefacts.    Regards, Smarak ... View more

I am facing similar issues. Please help me out if anyone has any solution to this. ... View more

I'm able to fix this .. In JSON Tree READER the configuration for `Schema Access Strategy` should be "Infer Schema" Input date format will be "yyyy-MM-dd HH:mm:ss.SSS'Z'" avro schema for the same will be { "name": "createdAt", "type": { "type": "long", "logicalType": "timestamp-millis" } }   ... View more

Hello bro @SAMSAL , were you successfully control the nifi component using postman? If yes, would it be okay to share your countermeasure. Currently encountering the same issue that you had. Thanks in advance.   ... View more

The issue was not related to the size of the queue, but instead to the fact that when to destination that we are sending those logs to had connectivity issues (which was causing quite a lot of timeout errors), NiFi was using a lot of a significant number of threads to retry sending the logs to the InvokeHTTP destination. This high usage of threads was causing ListenSyslog to not function properly - it was dropping the logs that it was supposed to receive. ... View more

Hello @sekhar1    We hope your Q was answered by  André. As such, We are marking the Post as Resolved. If the Link shared by André didn't fix the issue, Feel free to Update the Post likewise.    Regards, Smarak ... View more

Nice article,  But not working any more. Failing to find mariadb repo as mariadb 10 was archived.   ... View more

I've attempt to set the above in the java.security file and in the bootstrap I set the runtime variables as java.arg.20=-Djava.security.networkaddress.cache.ttl=60 java.arg.21=-Dsun.net.inetaddr.ttl=60 ... View more

You can get the id of the root process group and import the template there as well.   André ... View more

Hi @araujo  this link was really useful . But where can i get the password for newly created users. Without password how can new users access it . I am not able to find any documentation for that. i have checked in all the files as well and couldn't find any passwords ... View more

@wasabipeas  I can think of no way to force delete if it is blocking on a revision mismatch between nodes. Nothing here has anything to do with version control.  Is it always the same node reported in the pop-up message that fails to process the request? If so, have you verified the libs and version running on that one node match rest of cluster? If you go to the cluster UI and select "VERSIONS" tab, they all reflect same version? You could manually disconnect the one node that it keeps complaining about from the "NODES" tab. After it is disconnected, you could delete it from the cluster (Deleting the nodes does nothing flows or data on that node.  It will require a restart of that one node to get it to rejoin cluster). Once the node is removed form your cluster (temporarily), your cluster should reflect 10/10 connected nodes now in the status bar of the canvas UI. Check to see if your are still having revision issues with the process after reloading the page. If all looks good, you could access the filesystem of the currently disconnected and deleted node, stop the NiFi service on that node, and delete/rename the flow.xml.gz and flow.json.gz files.  Then start this node again. On startup, NiFi will inherit the flow from the cluster and in doing so get the cluster flows current revision for the problematic process group.  If problem persists, restart node that was deleted so that it rejoins the cluster. Then disconnected the currently elected cluster coordinator.  A new cluster coordinator will then be elected by zookeeper. Check to see if issue with process group is resolved. Reload your browser to force a page refresh. If issue is resolved, rejoin node to cluster via the cluster UI to see if issue returns.  If so, we at least know which is our problematic node.  You can of course, disconnect, delete, rename flow.xml.gz and flow.json.gz, and then restart node, just as we performed before so that flow is pulled from cluster on startup.  If issue still persists, there is something unique about this node.  Disk space ok?, any exceptions in logs?, while node may report same NiFi version, something different with contents of lib(s) folders (get a checksum and compare against other nodes). Hope this helps without needing to restart entire cluster, Matt ... View more

Thanks @SAMSAL  and @araujo for the responses.  The RouteOnAttribute is what I am using presently but it gets unwieldily after just a couple of route options.  Looks like I'm just gonna need to build a custom validator using the ExecuteScript processor.  Hopefully that scales.  ... View more

hi @araujo    the userPrincipalName of user livy is:   livy/hostname_livy_server@DOMAIN.LOCAL     the userPrincipalName of the livy-http user is:   livy-http@DOMAIN.LOCAL     running the command "kinit livy":     running the command "kinit livy-http":     running the "kinit" command with the keytab created for user livy:     running the command "kinit" with the keytab created for the user livy-http:     we've been facing this problem for months, we haven't found the solution yet. ... View more

Hi @araujo,   My apologies for coming back late.   The job reads from 2 Kafka sources and send the data to Kinesis stream (sink).   Thanks, Prabu. ... View more

@VenkatG Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks ... View more

Everything you do in the NiFi UI can also be done using the NiFi REST API. So if you want/need to automate it, it's totally possible and not difficult.   Cheers, André ... View more

@JimHalfpenny and @araujo thanks both of you for your help! The solution of creating a view with some kind of placeholders worked for me! ... View more

@rafy ,   Same approach. Just create the processor(s) and let the files flow through it 🙂   Cheers, André   ... View more

@Ahmed_Abuhaimed ,   Have you looked into change data capture functionality for Hana? https://help.sap.com/docs/SAP_DATA_INTELLIGENCE/1c1341f6911f4da5a35b191b40b426c8/023c75aedfdd4646934f2d9ccde5660a.html   Cheers, André   ... View more

@samrathal ,   Is seems that "subtract" only works for integers and your value is a long. The longSubtract function only works if longs are passed as parameters and I don't know if there's a way to specify a long literal in Jolt (I tried 60L but that doesn't work).   The following does a little bit more work but also achieves what you want:   [ { "operation": "modify-overwrite-beta", "spec": { "currenttime": "=toLong(${now():toNumber()})", "minute": "=toLong(60)" } }, { "operation": "modify-overwrite-beta", "spec": { "timeOneMinu": "=longSubtract(@(1,currenttime), @(1,minute))" } }, { "operation": "remove", "spec": { "minute": "" } } ]     Output: { "currenttime": 1662417935173, "timeOneMinu": 1662417935113 } Cheers, André ... View more

Hi  André,   With or without domain in the configuration, its taking default domain.  If we provide multiple domains also its not authenticating new one.   Thanks, Uday ... View more

Dear @araujo ,  Many thanks , yes . This configuration is already enabled and configured.     Any recommendation for troubleshooting and investigating issue for configuring kudu kerberos in cloudera 7.1.7 runtime is highly appreciated.    Thanks in advance,   ... View more

Yes, it works. Thank you so much!!   ... View more

@Omarb, Has any of the replies helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more

@araujo Thank you for the help.. It works.  ... View more

Yes, we have Cloudera subscription. We have contacted to support team, and they have asked us to use ' Maximum Timer Driven Thread Count  ' as 64. Earlier we were using this count as 280. we have tried to set it to 160 but it didn't help. So, we have reverted it back to 280 again.  ... View more

Thanks André. Our Application is running as http not https. See the result below.   [nifi1 ~]$ openssl s_client -connect ldap.dev.abcde:389 CONNECTED(00000003) write:errno=104 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 289 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session:     Protocol  : TLSv1.2     Cipher    : 0000     Session-ID:     Session-ID-ctx:     Master-Key:     Key-Arg   : None     Krb5 Principal: None     PSK identity: None     PSK identity hint: None     Start Time: 1662113057     Timeout   : 300 (sec)     Verify return code: 0 (ok) --- Please advise if there something we need to install/configure in our application   Thanks, Alvin ... View more

@araujo thank you! I had gotten around the issue by using a replaceText loop to search for capitals within' the keys 1 at a time and prepend underscores, followed by a jolt to lowercase all keys. You're script returns the same result, very impressed. Thanks again.   ... View more