Navigation Menu

Skip to content
This repository has been archived by the owner on Jun 25, 2021. It is now read-only.

Don't suppress parsec prune when relocation is in progress #1993

Merged

Conversation

madadam
Copy link
Contributor

@madadam madadam commented Jan 7, 2020

Closes #1963 .

Also includes a tiny refactoring.

jeanphilippeD
jeanphilippeD previously approved these changes Jan 7, 2020
Copy link
Contributor

@jeanphilippeD jeanphilippeD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. need soak testing.

octol
octol previously approved these changes Jan 7, 2020
Instead any unaccumulated/unconsensused `Relocate` and `RelocatePrepare` votes are carried over to the new parsec instance.
@madadam madadam dismissed stale reviews from octol and jeanphilippeD via 94413c7 January 7, 2020 15:36
@madadam madadam force-pushed the dont-suppress-prune-for-relocation branch from 01dc0b8 to 94413c7 Compare January 7, 2020 15:36
@jeanphilippeD jeanphilippeD merged commit d60e251 into maidsafe:fleming Jan 7, 2020
@madadam madadam deleted the dont-suppress-prune-for-relocation branch January 7, 2020 16:07
jeanphilippeD pushed a commit to jeanphilippeD/routing that referenced this pull request Jan 9, 2020
Fix aggressive_churn: [1221425541, 378878981, 107272102, 3204539950] at
dc2abe1.

Address issue introduced with maidsafe#1993: Ensure we filter out all completed
events.
Also improve logs for debuging.

Test:
Verify the seed is fixed.
soak test + clippy
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do not supress parsec prune when relocation is in progress
3 participants