Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

CRON on GetHDFS is initiating threads but unable to connect to Hadoop master

avatar
New Contributor

Hello Everyone,

We are facing below issue in our CFM.

Background: We have NiFi Flow which uses GetHDFS processor to fetch all the HDFS files and performs few transformation and put the data back to HDFS using putHDFS processor. The CRON used for this was: 0 0/45 06-19,21-05 1/1 * ? *

Now: Now based on the requirement we have changed the CRON schedule to "0 30 10-19 1/1 * ? *" (0 30 10-19 * * ? *) , the getHDFS processor runs at CRON schedule and also process the data on the day of change. But from next day/tomorrow onwards the processor is running/threads are intiated on all nodes based on CRON schedule however it does not process the data and gives a below warning.

Warning: Error while retrieving list of files due to DestHost:desport <master_hostname>:<port>     LocalHost:localport <worker_node>:<port>

Failed on Local Exception: java.io.IOException: Couldn't setup connection for <nifi_user>@principal to <master_hostname>

 

Does anyone recognise this issue, request to provide an inputs on this.

 

Thanks,

Sujit

1 ACCEPTED SOLUTION

avatar
New Contributor

Hello Community,

I have found a solution for this issue. The Authentication Expiration value was less than the gap between last run (today) and next first trigger (tomorrow), and that kerberos certificate was already expired and hence it was unable to run.

We have increased the Authentication Expiration period and the issue is resolved now.

Thanks,

Sujit

View solution in original post

1 REPLY 1

avatar
New Contributor

Hello Community,

I have found a solution for this issue. The Authentication Expiration value was less than the gap between last run (today) and next first trigger (tomorrow), and that kerberos certificate was already expired and hence it was unable to run.

We have increased the Authentication Expiration period and the issue is resolved now.

Thanks,

Sujit