This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
storage/localstore: Local Pinning fix for pinned chunks #2200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes issue #2195, to summarize GC was removing pinned chunks when it was not supposed to.
This is related to PR #2190 which was the incorrect fix for this bug, thanks to @jmozah for providing the correct fix for this situation.
The solution is to check if the chunk is in the pinIndex before inserting it into gcIndex, this avoids the GC removing the chunk in the first place.
Replaced in these files
mode_set.go
mode_get.go
mode_put.go
Also, the test
TestDBDebugIndexes
was corrected due to the pinned chunks now being avoided correctly.Test criteria were:
--pin
dd if=/dev/urandom of=output.txt bs=4096 count=40000 && /home/git/go/src/github.com/ethersphere/swarm/build/bin/swarm --bzzapi http://localhost:8503 up output.txt
The bug is also in Bee and it is fixed in a similar fashion