[SERVER-29709] Make LogicalSessionCache robust for limited environments Created: 19/Jun/17  Updated: 29/Jan/18  Resolved: 07/Sep/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: Gabriel Russell (Inactive)
Resolution: Duplicate Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-07-10, Platforms 2017-07-31, Platforms 2017-08-21, Platforms 2017-09-11
Participants:

 Description   

Users should be able to create and use sessions even when the node they are talking to cannot communicate with the session store. This requires some changes to the LogicalSessionCache:

  • SessionsCollection methods should return StatusWith so they can indicate networking errors
  • sessions that cannot be immediately started should have their records cached; during refreshes, the cache should re-attempt insertion of the new records


 Comments   
Comment by Samantha Ritter (Inactive) [ 07/Sep/17 ]

This work is being done as part of SERVER-28336.

Generated at Thu Feb 08 04:21:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.