noobaa-core
noobaa-core copied to clipboard
Dedup did not work fully when uploaded same file 4 times
Environment info
- Version: output of
git rev-parse HEAD
| package.json | UI - Deployment: N/A | Dev | VBox | ESX | GCloud | AWS
- Customer: N/A | QA | name
Actual behaviour
- Created a new bucket with policy of 1 pool with 3 nodes (all okay)
- Uploaded 3mb file (not video/no special replicas) that created 6 parts
- Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
- Uploaded same file ones again with a different name
- Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
- Saw in DB that there was a full dedup (everything correct till now)
- Uploaded same file ones again with a different name
- Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
- Saw in DB that we created 6 more chunks which means that we did not dedup 0%
- Afterwards did same thing with the 4th file and got a 100% dedup
Expected behavior
- I should see 100% all of the time and only have 6 chunks (like parts count of the first file)
Steps to reproduce
- Explained above
Screenshots or Logs or other output that would be helpful
(If large, please upload as attachment)
@nimrod-becker This is too old and stale by now. We should either reproduce on master or close.
Reproduced by Liran
I will add a unit test that writes same file repeatedly and verifies that it always finds dedup.
Per guy's comment, closing this one
Keeping open as a reminder to commit the test