Affects Version/s: 1.1.1
Fix Version/s: 1.2 GA
Pull Request URL:
Spring XD should be able to generate a new Kerberos ticket when start running a new job instead of renew the current one, because the current one could be expired or the renew time could be finished.
Running Spring-XD singlenode with a kerberized hadoop cluster on CDH 5.3.2. with JDK 1.7 and JCE 1.7.
The kerberos ticket policies are:
- expiration: 24 hours
- renew: 7 days
I need to keep the Spring XD server running constantly because my flows are always waiting for incoming files to be ingested into the HDFS, but the kerberos session expires if there aren't jobs to run before the expiration date. The expiration policies can't be changed due internal company policies.
Is there a way which Spring XD can generate a new ticket instead of renew the current one when a job or stream start executing?
The Spring XD server has configured the hadoop.properties like:
- Use servers.yml to change URI for namenode
- You can add additional properties in this file
#Connecting to Kerberized Hadoop (Spring XD doc configuration Appendix D)