@Raven01,   Yes, if you didn't update the "External Connection" informatiobn for the LASR Authorization Service in SAS Management Console. Check the current value in Application Management -> Configuration Manager -> SAS Application Infrastructure -> Visual Analytics 7.<X> -> Visual Analytics Services 7.<X> -> right-click on the LASR Authorization Service 7.<X> -> Properties -> External Connection. ... View more

@VladimirLaskov,   First of all, check HDFS cluster status:   hdfs dfsadmin -report   Something is wrong with the datanode running on cloudera-node2.example.loc.   You can use the following steps to enable advanced debugging for loading to HDFS from SAS: 1. Create a .tkmpi.personal file in the /home/ directory of the user invoking SAS or LASR: /home/userid/.tkmpi.personal 2. Insert the following line in the file: export HADOOP_LASR_STDERR_LOG=/tmp/hdfs_fail.txt 3. Copy the .tkmpi.personal file across hosts of the grid. /<PATH_TO_TKGRID>/bin/simcp /home/userid/.tkmpi.personal /home/userid 4. Perform the task or submit the code that generated the problem. From the example below: libname hdfs SASHDAT SERVER="headnode.unx.lax.com" INSTALL="/local/install/TKGrid" PATH="/hps/user"; data hdfs.mydata(replace=yes); set sashelp.class; run; 5. Inspect the /tmp/hdfs_fail.txt log. A clean log looks like this: yy/mm/dd hh:mm:ss INFO hadoop.BaseService: Starting embedded NameNodeService yy/mm/dd hh:mm:ss INFO hadoop.BaseService: Starting NameNodeService yy/mm/dd hh:mm:ss INFO hadoop.BaseService: Data dirs: [/local/install/hadoop/hadoop-data] yy/mm/dd hh:mm:ss INFO hadoop.BaseService: Ready to accept commands yy/mm/dd hh:mm:ss INFO hadoop.BaseService: Processing command 9 /mm/dd hh:mm:ss INFO hadoop.BaseService: ConcatRequest [fileName=/hps/user/mydata.sashdat, flags=1, permissionsMask=774, fileParts=[FilePartInfo [fullPath=/hps/user/mydata.sashdat-12.34.567.89.sashdat, numBlocks=1], ... The fileparts= details are repeated for each grid host. yy/mm/dd hh:mm:35 INFO hadoop.BaseService: Action 9 complete 6. Check the head node first. If that log is clean, you should check the debug log files on other nodes. 7. When debugging is complete, remove the .tkmpi.personal file across the grid. /<PATH_TO_TKGRID>/bin/simcp /home/userid/.tkmpi.personal Otherwise the debugging option may cause performance issues. ... View more

@LDYL, how to reduce the size of dataset on LASR, however with the star schema being applied ? There is no way. Can I somehow combine compression with star schema? No. ... View more

@LDYL,   Each column in the LASR server is padded to an 8-byte boundary. If the variable you are adding is not a multiple of 8 bytes, the variable will be padded to an 8-byte boundary.   Read this: https://en.wikipedia.org/wiki/Data_structure_alignment ... View more

@Raven01,   That message can be ignored. If you see nothing else there, that means "proc lasr" or SASIOLA engine, whichever you using, was not able to connect to LASR Authorization Service.   Have you recently made any changes on the middle tier? For an example, maybe you've configured HTTPS (SSL)? Also, make sure that you have specified a valid META options. ... View more

@Raven01,   Have you seen any errors in /<SASConfig>/Lev<X>/Web/Logs/SASServer12_1/SASLASRAuthorization7.<X>.log on the middle tier? ... View more

@slthiya4,   The Work library is the temporary library that is automatically defined by SAS at the beginning of each SAS session or job. The Work library stores temporary SAS files that you create, as well as files created internally by SAS.   The WORKINIT and WORKTERM system options control the creation and deletion of the Work library. For more information, see WORKINIT System Option in SAS System Options: Reference and WORKTERM System Option in SAS System Options: Reference. ... View more

@DavidGQ,   Have you seen any errors in the "Last Action Log"? Please do right-click on the LASR server -> Last Action Log. ... View more

@dianevictoriap,   Interactive reload depend on how a table was initially loaded. Only those tables are eligible for interactive reload:   Tables that were interactively loaded. Output from data queries.* Output from LASR star schemas.* SAS data sets that were imported from a server * Any input LASR tables must be available (loaded). ... View more

@nhvdwalt,   Sure, keep me posted. ... View more

@nhvdwalt,   Ensure that the krb5 libs (libkrb5.so, libcom_err.so, libk5crypto.so, and libkrb5support.so) are in the default directories. On 64-bit platforms, the directories are /lib64, /usr/lib64, and /usr/local/lib64. If the libs are not in these directories, specify the directories in the LSB_KRB_LIB_PATH= parameter. You can specify multiple paths, separated by blanks, commas, or semicolons.   Have you restarted LSF after changing lsf.conf?   If yes, please add these loggers to /<SASConfig>/Lev<X>/ObjectSpawner/logconfig.xml:   <logger name="Audit.Authentication"> <level value="Trace"/> </logger> <logger name="App.tk.tkegrid"> <level value="Trace"/> </logger> In the LSF configuration file, add these entries:   LSB_LOG_MASK=LOG_DEBUG LSB_DEBUG_CMD="LC2_KRB" LSB_CMD_LOGDIR=logging_directory LSF_LOG_MASK=LOG_DEBUG LSF_DEBUG_CMD="LC2_KRB" LSF_CMD_LOGDIR=logging_directory Restart both the object spawner and LSF, repeat a problem and send to me log files for further analysis. ... View more

@nhvdwalt,   Thanks for your response. That filename is not valid. That is KRB5CCNAME for gridRun, not for LSF. First of all, make sure that you have no scripts that can potentially change KRB5CCNAME in WorkspaceServer_usermods.sh. Second, are you sure that LSF ticket wasn't created in /tmp directory?   ls -lrt /tmp/lsf* | grep <YOUR_NAME> Also, are you using MIT libraries or third-party software such as Centrify? ... View more

@nhvdwalt,   What is the current value of KRB5CCNAME on the execution host?   %put KRB5CCNAME: %sysget(KRB5CCNAME); ... View more