ringpop-go v0.5.0 Release Notes

    • ๐Ÿ”‹ Feature: Automatic healing of fully partitioned rings that could be cause by temporary network failure. #135 #128 #129
    • ๐Ÿ›  Fix: Fullsyncs are now executed in both directions to prevent persistent asymmetrical partitions. #134
    • ๐Ÿ›  Fix: Overcome protocol incompatibilities in the dissemination of tombstones for the reaping of faulty nodes. #133 #132
    • ๐Ÿ›  Fix: Leaking goroutines on an error response after a timeout. #140
    • ๐Ÿ”จ Maintainability: Refactor of internal use of the Discovery Provider. #130
    • โœ… Testing: Pin mockery to a specific version for testing stability. #136
    • โœ… Testing: Add Go race detector on CI. #137

    ๐Ÿš€ Release notes

    ๐Ÿš€ Deploying from older versions

    ๐Ÿš€ It is advised to complete the deployment of this version within 24 hours after โฌ†๏ธ the first node is upgraded. Since the reaping of faulty nodes is added to this ๐Ÿš€ release a node that upgraded to this version will mark all the faulty members of the ringpop cluster as tombstones (the new state introduced for the reaping of ๐Ÿš€ faulty nodes) 24 hours after the deploy. If older versions of ringpop run in a cluster that starts declaring these tombstones the cluster will jump in endless fullsyncs mode. Ringpop operates normally under these conditions but extra load on both network and CPU are in effect during this time. The fullsyncs will โฌ†๏ธ automatically resolve as soon as all members are upgraded to this version. Same โช might happen during a partial rollback that operates for a longer period of time.