Absolute brilliance @alexal !!   This is exactly what I was looking for. Long story short, the trace clearly shows a timeout against the first KDC listed in krb5.conf. I'll chat to the AD team to see why that KDC is offline. This is a production environment, so all services should be available. So 90 of the 94 seconds is spent waiting for an offline KDC. Once the request is sent to the second KDC, the Hadoop connection is instant.   Interesting though, although Java 8 also says retries=3, it doesn't actually try 3 times. After the first try fails (30 seconds) it goes to the second KDC. So again, 30 out of the 34 seconds is spent waiting for an offline KDC. But that's just a side note. I'm confident that if the first KDC is online, we'll have almost immediate connection.   Thanks a mile for the help ! ... View more

Thanks @alexal   Yes, if you have any suggestions about how to troubleshoot, I'll appreciate it.   Regards, ... View more

Thanks @alexal, it worked perfectly ! I recompiled the code and can now test the connections successfully.   To get back to the original question....   I found that the connection to Hadoop takes 94 seconds with Java 7 (SAS supplied) and only 34 seconds with Java 8 (Red Hat supplied). Although we cannot change the SAS version, at least I have a reasonable explanation now. I guess some of the 34 seconds are taken up by Kerberos when the tickets are obtained initially. So overall, it's manageable. The key is to ensure the login timeout is set on the libname statement, since the login time is still outside of the default 30 seconds.   Thanks for the help.       ... View more

Hi @KenGahagan   Has there been updates to this ?   Thanks, ... View more

Thanks @alexal   I managed to get the script working. I had to specify the below parameters as well since we are using Kerberos:   KRB5CCNAME -Djavax.security.auth.useSubjectCredsOnly=false   Does the script have the ability to take a schema name as parameter ? It defaults to the 'default' schema to which I don't have USE access, but I have access to other schemas.   The problem doesn't seem to be authentication since it fails almost immediately if the wrong credentials are provided. The lag seems be between successful authentication and the point where it runs the 'show tables' command.   Btw...I can't access the README file for this script. ... View more

 I would suggest that you refer this question entirely to your SAS Account Executive (AE).   This forum might be able to provide some defaults answers, but licensing contracts are very circumstantial and are mostly negotiated on a customer by customer basis and this forum cannot comment on any licensing matters. ... View more

When you say limit the size, do you mean the size of the LASR analytics server i.e. the in-memory server, or something else ? ... View more