2017 IEEE 36th Symposium on Reliable Distributed Systems (SRDS) 2017
DOI: 10.1109/srds.2017.23
|View full text |Cite
|
Sign up to set email alerts
|

Reconfiguring Parallel State Machine Replication

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0
11

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 33 publications
(25 citation statements)
references
References 26 publications
0
14
0
11
Order By: Relevance
“…Reconfiguration of distributed systems have been extensively studied in the past as it finds applications in cluster membership changes, atomic storage, file systems, replicated state machines, and rolling upgrades . The most common types of reconfigurable services are atomic storage that supports reads and writes and replicated state machine that supports generic commands, like transactions …”
Section: Related Workmentioning
confidence: 99%
“…Reconfiguration of distributed systems have been extensively studied in the past as it finds applications in cluster membership changes, atomic storage, file systems, replicated state machines, and rolling upgrades . The most common types of reconfigurable services are atomic storage that supports reads and writes and replicated state machine that supports generic commands, like transactions …”
Section: Related Workmentioning
confidence: 99%
“…In both cases, clients tag requests with the ids of the worker threads that will execute the requests. In [1], a scheduler thread delivers requests in total order and assigns each request to the worker responsible for the execution of the request. In [24], there is no scheduler involved; the atomic broadcast primitive uses the request tag to deliver requests directly to worker threads at the replicas.…”
Section: Early Schedulingmentioning
confidence: 99%
“…We adopt the following replica execution model, which extends the more restrictive model proposed in [1]:…”
Section: Replica Execution Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…Dois comandos são ditos não conflitantes caso a escrita de um não ocorra no mesmo dado em que a leitura ou escrita do outro, caso contrário são conflitantes. Para maximizar o ganho de desempenho, faz-se necessário explorar o balanceamento do trabalho entre as threads, assim como minimizar o impacto causado pela necessidade de sincronização que se dá pela existência de comandos conflitantes [7].…”
Section: Introductionunclassified