Allow coding shred index to be different than data shred index #7438
+186
−53
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.
Problem
First coding shred index must be same as the first data shred index in an FEC block. This prevents an FEC block to have more number of coding shreds than number of data shreds (as that'll cause the last coding shred index to overlap with the data shred index of the next FEC block).
Summary of Changes
Decoupled the coding shred index from data shred index. Also, updated erasure recovery code to use the new indexing scheme.
Reference #7428