Support #8322: Issues (R Studio ) - D4Science Infrastructure - D4science

Custom queries

03. VRE Plan
04. All Projects Deliverables
04. All Projects Milestones
06. D4Science Projects Activities
All open Issues
D4Science Infrastructure Upgrade
My InProgress Tasks
My Paused Tasks
My Watched Tasks
Not Closed Assigned To Me
Not Closed Assigned To Me (No Releases, No Project Tasks)
Not Closed Opened by Me
Open Issues
Upgrade Plan
Upgrade Plan Clear

Actions

Copy link

Support #8322

closed

Issues (R Studio )

Added by TAHA IMZILEN almost 8 years ago. Updated almost 8 years ago.

Status:

Closed

Priority:

High

Assignee:

Lucio Lelii

Category:

Start date:

May 11, 2017

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Infrastructure:

Production

Description

Dear Gianpaolo,

Something is going wrong with Rstudio since yesterday afternoon.

On RprototypingLab, I can not open R studio.I get this message 'Successfully logged out from Rstudio' and The tab closes after a few seconds .

and on RStudioLab, We get memory allocation errors when we run scripts

can you help us please ... ?

Thank you
Taha

Subtasks 1 (0 open — 1 closed)

Support #8489: Issues memory (R Studio )

Closed

_InfraScience Systems Engineer

May 11, 2017

Actions

History
Notes
Property changes

Actions

Copy link

Updated by Gianpaolo Coro almost 8 years ago

Assignee changed from Gianpaolo Coro to Lucio Lelii

Actions

Copy link

Updated by Lucio Lelii almost 8 years ago

The problem with RpototipingLab VRE was due to an error with the LDAP authentication and it is solved now.

About the memory allocation problem I don't know what is happening because nothing changed on that node, Did the same script work in the past ?

Actions

Copy link

Updated by Andrea Dell'Amico almost 8 years ago

I just killed a lot of old stale sessions that used most of the available memory. Can you try again?

Actions

Copy link

Updated by Julien Barde almost 8 years ago

How can we know when such a situation happens and can we get the list of old sessions and kill them ?

A single compilation of the knitr document is very demanding for memory and as we work together we split the resources of the RStudio instance with different persons (and multiple sessions per person I guess).

Actions

Copy link

Updated by Massimiliano Assante almost 8 years ago

Project changed from 8 to D4Science Infrastructure
Target version changed from RStudio elastic management to UnSprintable
Infrastructure Production added

Actions

Copy link

Updated by Andrea Dell'Amico almost 8 years ago

Status changed from New to Feedback
% Done changed from 0 to 100

Julien Barde wrote:

How can we know when such a situation happens and can we get the list of old sessions and kill them ?

A single compilation of the knitr document is very demanding for memory and as we work together we split the resources of the RStudio instance with different persons (and multiple sessions per person I guess).

I don't think that rstudio gives such a possibility. We are thinking about a way to automatically kill old, stale sessions, or at least to report them.

Actions

Copy link