You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this issue already tracked somewhere, or is this a new report?
I've reviewed existing issues and couldn't find a duplicate for this problem.
Current Behavior
There is recently a DSE issue reported by Earthdata Login (EDL) during data download requests involving large amount of granules through EarthAccess. One issue was traced to EarthAccess creating a new session for each download instead of reusing the existing session cookie, which is intended to reduce the number of requests to EDL by the DAAC data distribution endpoint (TEA).
Expected Behavior
The session cookie should be reused between download requests from the same thread.
There is an open PR trying to address this issue: #909
mfisher87
changed the title
[BUG] {{ Session reuse between download requests within the same thread }}
[BUG] Session reuse between download requests within the same thread
Jan 5, 2025
The PR was merged on Friday, if everything goes as planned we'll release 0.13.0 this week and we could tell the IBM people to try it and we'll close this issue if we see no spikes in EDL.
Is this issue already tracked somewhere, or is this a new report?
Current Behavior
There is recently a DSE issue reported by Earthdata Login (EDL) during data download requests involving large amount of granules through EarthAccess. One issue was traced to EarthAccess creating a new session for each download instead of reusing the existing session cookie, which is intended to reduce the number of requests to EDL by the DAAC data distribution endpoint (TEA).
Expected Behavior
The session cookie should be reused between download requests from the same thread.
Steps To Reproduce
By running the following scripts:
TEA was observed to make separate EDL requests for each download instead of reusing the session cookie as designated.
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: