English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Distributed consensus is a key enabler for many distributed systems includingdistributed databases and blockchains. Canopus is a scalable distributedconsensus protocol that ensures that live nodes in a system agree on an orderedsequence of operations (called transactions). Unlike most prior consensusprotocols, Canopus does not rely on a single leader. Instead, it uses a virtualtree overlay for message dissemination to limit network traffic acrossoversubscribed links. It leverages hardware redundancies, both within a rackand inside the network fabric, to reduce both protocol complexity andcommunication overhead. These design decisions enable Canopus to support largedeployments without significant performance degradation.  The existing Canopus protocol is resilient in the face of node andcommunication failures, but its focus is primarily on performance, so does notrespond well to other types of failures. For example, the failure of a singlerack of servers causes all live nodes to stall. The protocol is also open toattack by Byzantine nodes, which can cause different live nodes to conclude theprotocol with different transaction orders. In this paper, we describe RCanopus(`resilent Canopus') which extends Canopus to add liveness, that is, allowinglive nodes to make progress, when possible, despite many types of failures.This requires RCanopus to accurately detect and recover from failure despiteusing unreliable failure detectors, and tolerance of Byzantine attacks. Second,RCanopus guarantees safety, that is, agreement amongst live nodes oftransaction order, in the presence of Byzantine attacks and networkpartitioning.

RCanopus: Making Canopus Resilient to Failures and Byzantine Faults