[EXTDAM-116] S3: Strange behaviour deleting a folder Created: 29/Apr/20 Updated: 20/Jul/20 Resolved: 26/May/20 |
|
| Status: | Closed |
| Project: | External DAMs |
| Component/s: | s3 |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jesus Alonso | Assignee: | Jesus Alonso |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Epic Link: | DAMs backend |
| Sprint: | Add-Ons 38 |
| Story Points: | 1 |
| Description |
|
Step to reproduce
Possible explanation: S3 is eventually consistent and the deletion of the second folder is not yet committed.
AC
|
| Comments |
| Comment by Jesus Alonso [ 14/May/20 ] |
|
It turns out it is a cache problem. In the previous above we have the following entries in cache:
When we delete /folder1, only the cache for /bucket (the parent) is being evicted. Thus, if we create again /folder1, as it is already cached, the cached content is used. Solution could be evicting the current folder too in deleteFolder. |