About brendanodwyer

brendanodwyer · ‎09-07-2016

We have been testing and load balancing our Grid in our TEST environment before going to PROD and it doing we discovered something odd with the way SAS Studio behaves with GRID. As a note we are using Grid-Launched Workspace Servers. When we tested GRID with EG we noticed that SAS will spin up 1 job slot on GRID, which is fine as this is expected behavior; however, with SAS Studio we are seeing two job slots being occupied when SAS Studio starts. We have watched the process with bhosts and bqueues and made sure that it is consistently happenening. Has anyone seen or had this happen to them in their environment? Side-note: I was the only one in the environment when I was producing/re-producing this behavior so I know that one SAS Studio Session causes 2 job slots to be occupied.

brendanodwyer · ‎08-16-2016

So that helps us with how we can configure the underlying storage. So if i understand you correctly, we can share all of SASHome where SAS is installed across every node in the cluster, but for SASConfig only share this directory(technically a separate mount for this to work) with the Compute Tier and Metadata Server. For the Mid-Tier it should be able to see the /SASHome where the installs are, and each /SASConfig should be local to each node. Do you have documentation that says how to configure the Mid-Tier in this way? I have looked at all the documentation that i can find and cannot find any documentation referencing your recommendation.

brendanodwyer · ‎08-11-2016

So we are sharing all of those currently, what i want to know is whether or not we should share the Lev1 directory amongst the tiers. We tried to install all of them under the same area, and hit nothing but problems.

brendanodwyer · ‎08-10-2016

Bruno, Are those codes specific to client applications? Just curious. Assuming so.

brendanodwyer · ‎08-10-2016

So my colleagues and I have gotten GRID fully installed with a single metadata server and single mid-tier server, but when we reinstalled and tried to cluster the mid tier we hit a snag on the install which I'm guessing is related to a more general question that we have had; should the SAS-Installation and SAS-Configuration directories be shared across the whole group of machines? Currently we have both installed in a location in UNIX shared across all nodes in the cluster at /sas/ under SASConfig and SASHome, so that each node can see the configurations and binaries of each other node. Is this how we should set it up? I have scoured piles of documentation looking for how to set this up correctly and have only found one vague reference?

brendanodwyer · ‎07-27-2016

We have Python code that reassembles the SAS code and does analysis on what it is doing. We previoulsy used a similar situation to parse our RTrace logs in an old environment. As far as management is concerned, the logs are centrally located and reconciled to our Hadoop environment so that we can catalog and parse them at will. The high compression ratio of the logs has made them extremely easy to store and rextract into files that the Python code can then mine.

brendanodwyer · ‎07-27-2016

We are using SASV9_OPTIONS to make sure that altlog is recorded across the Grid environment. Since this option is set in UNIX/LINUX we can make sure we have what we need to make the log collision proof accross the cluster. Since some sessions are logged and others arent under Grid-Launched Workspace Servers using -ALTLOG we are using the Environment Manager Postgres instance to our advantage to record and reconcile instances of each type of session so that we can track what is being done in the environement at all times. The default sas executable at !SASROOT/sas has been modified to accomodate these changes and log all uses of that executable.

brendanodwyer · ‎07-27-2016

We found an alternate solution that allows us to collect the logs on a permanent basis. Thank you for the assistance.

brendanodwyer · ‎07-22-2016

So our workspace servers are grid launched, and the logs are enabled, we havent turned on TRACE yet but that is my next step to see what TRACE will tell us, but in the standard logging configuration we havent been able to see that the workspace server was even launched. We get this error in EG [Error] Failed to start the server. [Error] The launch of server SASApp - Workspace Server for user <XXXXXX> failed.

brendanodwyer · ‎07-22-2016

We have an Audit, Compliance, and Regulatory requirement to begin tracking, quite literally, everything in our SAS Environment that is running. The Requirement is more granular than aggregates surrounding PROC's and SAS Products, that we do have and get from Environment Manager.

brendanodwyer · ‎07-22-2016

We have tried to inject the parameter before the sas command that gets executed on SAS EG Launch. We also tried to put it in !SASROOT/sasv9.cfg and !SASROOT/sasv9_local.cfg. Both dont seem to work when we tried to have it launch EG and connect into the Grid, which as I understand it is when the Workspace Server is being launched by the GRID.

brendanodwyer · ‎07-21-2016

I have a requirement to set the alt log so that we retain a complete copy of anything running in and on the Grid. Including everything that EG or SAS Studio Executes. I have tried setting it in a few places and every time I set it and try to launch a workspace server via grid, the whole infrastructure just dies. Have to reboot everything. I do have a wrapper script that does set it when I use the SAS Grid Client Utility.

Online Status	Offline
Date Last Visited	‎09-29-2016 06:01 PM

SAS Studio occupies 2 job slots in SAS 9.4M3 Grid

Re: SAS Clustered Storage Grid Install

Re: SAS Clustered Storage Grid Install

Re: How do I measure the use of the SAS Add In?

SAS Clustered Storage Grid Install

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

SAS Clustered Storage Grid Install

SAS Studio occupies 2 job slots in SAS 9.4M3 Grid

Re: SAS Clustered Storage Grid Install

Re: SAS Clustered Storage Grid Install

Re: How do I measure the use of the SAS Add In?

SAS Clustered Storage Grid Install

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Re: Using ALTLOG with SAS EG and Studio, in Grid

Using ALTLOG with SAS EG and Studio, in Grid