-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Platforms 2017-07-10, Platforms 2017-07-31, Platforms 2017-08-21, Platforms 2017-09-11
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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