Actions
Bug #19192
closedWebDAVCache not performing as expected for S3 requests
Added by Tom Clegg over 2 years ago. Updated over 2 years ago.
Story points:
-
Release:
Release relationship:
Auto
Files
keep-web (11 MB) keep-web | dev build at commit 042f0d37dacebddef9d2d7232fa2e5b9922a9451 | Tom Clegg, 06/13/2022 06:15 PM | |
keep-web (11 MB) keep-web | dev build at commit 65c1517193b5039769f288e84a11d1ebfddbf031 | Tom Clegg, 06/20/2022 04:44 PM | |
keep-web (11 MB) keep-web | dev build at commit b5db4b70878a3907db3691b71979e6e65511a12c | Tom Clegg, 06/21/2022 03:22 AM |
Updated by Tom Clegg over 2 years ago
Debug logging indicates (*cache)pruneSessions() is not running, which causes expired sessions to get stuck in the cache forever. I'm guessing there's a situation where fs.MemorySize() deadlocks, and once that happens, pruneSessions can't continue/resume, and we effectively have no cache.
SIGABRT would produce a stack trace to confirm this and show where it's getting stuck.
Updated by Tom Clegg over 2 years ago
- File keep-web added
19192-fix-deadlock @ dab0c5596e39dc455d88bba797717e829fe5caf5 -- developer-run-tests: #3177
Fixes a lock-ordering bug in lookupnode causing deadlock on concurrent open() and readdir() calls in the same lookupnode (project) directory.
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-06-22 Sprint to 2022-07-06
Updated by Tom Clegg over 2 years ago
- Related to Idea #19205: In Go services, monitor request times and record when they continue processing after client disconnects, or exceed a maximum request time added
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-07-06 to 2022-07-20
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-07-20 to 2022-07-06
Updated by Peter Amstutz over 2 years ago
- Status changed from In Progress to Resolved
- Category set to Keep
Updated by Tom Clegg over 2 years ago
- Related to Bug #19368: [keep-web] [S3] slow requests caused by logUploadOrDownload added
Actions