Re: Regarding AWScredentialproviderService
Hi , please ignore my previous mail.as i got the answer. On Wed, 30 Oct, 2019, 8:16 AM sanjeet rath, wrote: > Hi, > I have built custom controller service(AWS-CREDENTIAL-CONTROLER-SERVICE) > and use this one in processor service(NIFI-AWS-SERVICE).for puts3Object. > In this controller service i have used custom parameters to connect to aws > and getting token , also using this token i am able to to use connect AWS > and able to upload object using puts3object processor. > > But i am not able to understand few things , > 1) How token refresh works in custom controller service. > 2) Does it refresh after time out. > > Regards, > Sanjeet Kumar Rath, > mob- +91 8777577470 > >
Regarding AWScredentialproviderService
Hi, I have built custom controller service(AWS-CREDENTIAL-CONTROLER-SERVICE) and use this one in processor service(NIFI-AWS-SERVICE).for puts3Object. In this controller service i have used custom parameters to connect to aws and getting token , also using this token i am able to to use connect AWS and able to upload object using puts3object processor. But i am not able to understand few things , 1) How token refresh works in custom controller service. 2) Does it refresh after time out. Regards, Sanjeet Kumar Rath, mob- +91 8777577470
Re: Nifi Single Instance mode to Cluster Mode
(Removing dev@; only use one list please) Hi Bimal, That error generally means the encryption key used to decrypt the sensitive value was not correct — i.e. not the key used to encrypt the value originally. It sounds like you will need to contact the vendor for this specific issue. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Oct 28, 2019, at 12:12 PM, Bimal Mehta wrote: > > Hi, > > We are doing a migration from a single instance NiFi to a NiFi cluster mode > (with 3 nodes) using Cloudera Manager. > After staring all the 3 nodes from Cloudera Manager, only 1 shows connected > and the others appear disconnected. > In the log file for the 2 nodes that are showing disconnected, we get the > following error: > 455 ERROR org.apache.nifi.controller.serialization.FlowFromDOMFactory: There > was a problem decrypting a sensitive flow configuration value. Check that the > nifi.sensitive.props.key value in nifi.properties matches the value used to > encrypt the flow.xml.gz file > org.apache.nifi.encrypt.EncryptionException: > org.apache.nifi.encrypt.EncryptionException: Could not decrypt sensitive > value > > I am unable to update the nifi.sensitive.props.key as it is generated by > Cloudera Manager when we start the nodes. > Any suggestions? > > Thanks > Bimal Mehta
Regarding limit of Puts3Object processor
Hi Team, I have question, why does puts3Object limit itself 14 msgs/Sec. can identify bottlenecks using some logs. Any code explanation will be very helpful. Thanks -- Sanjeet , mob- +91 8777577470
