Our company uses a single RStudio Server pro cluster in load balancing setup to serve all our R users in our division. We are seeing interest from other parts of the company in using R, and I'm working on planning the expansion of our cluster to those other groups. We have several different divisions in our company, and our R users will each be associated with one of those divisions. We would like to have a single heterogeneous cluster where we have a mix of nodes "owned" by the different divisions (so server costs can be allocated accordingly, and we're isolating data and risk of downtime caused by heavy usage by users from one division).
We can certainly load balance users to specific nodes based on user groups and have that working in our tests so far. My questions are as follows:
- Has anyone had experience with this heterogeneous setup in a single cluster before? Or do you simply create multiple clusters, one for each division? There are obviously pros and cons to each approach.
- For the users who actually end up doing work across multiple divisions (small but growing set of users), is it possible to make R sessions in the workspace manager "sticky" so that when you launch a suspended session it will spin up on the proper set of nodes? Or is there a way to isolate the ~/.rstudio/sessions folder which stores session history and info, so that a user only sees projects associated with a particular division?
Any other general thoughts or advice you may have as we make this step from supporting one set of R users to supporting many would be appreciated.