Sessions(if created) are orphaned by notebook auto termination process
· 2 min read
Sessions are remote apache spark runtime environments which can be created and managed in notebook for spark job development. with auto termination of notebook process, the active sessions are not being killed and causing additional cost for orphaned sessions until it reaches the session timeout(default is 48hours).
Affected Versions: 2.1
Fix Version: 2.2
Root cause(s)
Auto termination process was not considering the termination of sessions when it is stopping the notebook.
Impact
Account accrues additional cost for the orphaned sessions.
Mitigation
Users can manually check the sessions tab under the notebook details page for any active sessions and stop them.
Timeline
gantt
title Timeline
dateFormat YYYY-MM-DD
tickInterval 1day
axisFormat %b-%d
todayMarker off
section Tracker
%% update the ticket number and date of bug report
CLOUD-3199 : done, 2023-04-02, 0d
section Identification
Reported : crit, des1, 2023-04-02, 1d
section Mitigation
%% Update number of days took for each step below
Bug fixed: crit, done, 2023-04-04, 1d
section Delivery
%% update the date of each step below
Testing completed: milestone, 2023-04-11, 0d
- 2023-04-02: Bug reported/identified (CLOUD-3199)
- 2023-04-04: Bug triaged
- 2023-04-04: Bug fixed
- 2023-04-11: Testing completed
- 2023-06-01: Planned for Release v2.2