HTML Microdata document

This HTML5 document contains 134 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

Prefix	IRI
dbpedia-de	http://de.dbpedia.org/resource/
dcterms	http://purl.org/dc/terms/
dbpedia-da	http://da.dbpedia.org/resource/
yago-res	http://yago-knowledge.org/resource/
dbo	http://dbpedia.org/ontology/
foaf	http://xmlns.com/foaf/0.1/
dbpedia-ko	http://ko.dbpedia.org/resource/
dbpedia-hu	http://hu.dbpedia.org/resource/
dbpedia-es	http://es.dbpedia.org/resource/
n7	https://global.dbpedia.org/id/
yago	http://dbpedia.org/class/yago/
dbt	http://dbpedia.org/resource/Template:
dbpedia-uk	http://uk.dbpedia.org/resource/
rdfs	http://www.w3.org/2000/01/rdf-schema#
freebase	http://rdf.freebase.com/ns/
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
owl	http://www.w3.org/2002/07/owl#
dbpedia-vi	http://vi.dbpedia.org/resource/
dbpedia-it	http://it.dbpedia.org/resource/
dbpedia-zh	http://zh.dbpedia.org/resource/
wikipedia-en	http://en.wikipedia.org/wiki/
dbp	http://dbpedia.org/property/
dbc	http://dbpedia.org/resource/Category:
prov	http://www.w3.org/ns/prov#
xsdh	http://www.w3.org/2001/XMLSchema#
n5	http://dbpedia.org/resource/Enduro/
wikidata	http://www.wikidata.org/entity/
gold	http://purl.org/linguistics/gold/
dbr	http://dbpedia.org/resource/
dbpedia-ja	http://ja.dbpedia.org/resource/
n14	http://dbpedia.org/resource/X/

Statements

Subject Item: dbr:Bigtable
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Versant_Object_Database
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Durability_(database_systems)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Three-phase_commit_protocol
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Commitment_ordering
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: n5:X
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Enterprise_application_integration
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Global_serializability
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Gossip_protocol
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:MySQL
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Concurrency_(computer_science)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Concurrency_control
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Apache_Ignite
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Application_checkpointing
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Commit_(data_management)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Microservices
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Butler_Lampson
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:C._Mohan
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:knownFor: dbr:Two-phase_commit_protocol

Subject Item: dbr:Tuxedo_(software)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Data_(computer_science)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Web2py
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Distributed_algorithm
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Distributed_concurrency_control
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Document-oriented_database
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:ACID
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Actor_model
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Actor_model_and_process_calculi
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Database
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Atomic_commit
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: n14:Open_XA
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:COMMIT_(SQL)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:PostgreSQL
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Open_Cobalt
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Mashup_(web_application_hybrid)
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Multi-master_replication
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Two-phase
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageDisambiguates: dbr:Two-phase_commit_protocol

Subject Item: dbr:Two-phase_commit_protocol
rdf:type: yago:System104377057 dbo:Software yago:WikicatComputerNetworks yago:PhysicalEntity100001930 yago:Instrumentality103575240 yago:Artifact100021939 yago:ComputerNetwork103085333 yago:Object100002684 yago:Whole100003553 yago:Network103820728
rdfs:label: Commit-Protokoll Two-phase commit protocol Commit de dos fases Двофазна транзакція 2相コミット二阶段提交 2단계 커밋 프로토콜 Protocollo di aggiornamento a due fasi
rdfs:comment: Nelle reti di calcolatori e nei database, il protocollo di aggiornamento a due fasi (conosciuto come 2PC - Two-phase commit protocol) è un algoritmo distribuito che comprende tutti i nodi in un sistema distribuito per convalidare una transazione. Il protocollo deriva da tutti i nodi che convalidano la transazione o la fanno abortire, anche nel caso di errori di rete o dovuti ai nodi. Comunque sia, in base al lavoro svolto da Skeen e Stonebraker, il protocollo non gestirà più di un errore alla volta. In transaction processing, databases, and computer networking, the two-phase commit protocol (2PC) is a type of atomic commitment protocol (ACP). It is a distributed algorithm that coordinates all the processes that participate in a distributed atomic transaction on whether to commit or abort (roll back) the transaction. This protocol (a specialised type of consensus protocol) achieves its goal even in many cases of temporary system failure (involving either process, network node, communication, etc. failures), and is thus widely used.However, it is not resilient to all possible failure configurations, and in rare cases, manual intervention is needed to remedy an outcome. To accommodate recovery from failure (automatic in most cases) the protocol's participants use logging of the protocol' Двофазна транзакція — патерн проєктування, який дозволяє координувати транзакції здійснені до різних баз даних у вигляді однієї операції. 트랜잭션 처리, 데이터베이스, 컴퓨터 네트워크에서 2단계 커밋 프로토콜(two-phase commit protocol, 2PC)은 원자적 커밋 프로토콜(ACP)의 일종이다. 트랜잭션을 커밋할지, 아니면 롤백할지에 대해 분산 원자적 트랜잭션에 관여하는 분산 알고리즘의 하나이다. (특별한 종류의 ) 이 프로토콜은 수많은 종류의 일시적 시스템 문제(프로세스, 네트워크 노드, 통신 등)에도 목표를 수행하므로 널리 이용된다. 그러나 잠재적인 모든 문제 구성을 복구할 수 있는 것은 아니며, 드문 경우 문제 해결을 위해 사용자(시스템의 관리자)의 간섭이 요구된다. 二阶段提交（英語：Two-phase Commit）是指在计算机网络以及数据库领域内，为了使基于分布式系统架构下的所有节点在进行事务提交时保持一致性而设计的一种演算法。通常，二阶段提交也被称为是一种协议（Protocol）。在分布式系统中，每个节点虽然可以知晓自己的操作时成功或者失败，却无法知道其他节点的操作的成功或失败。当一个事务跨越多个节点时，为了保持事务的ACID特性，需要引入一个作为协调者的组件来统一掌控所有节点（称作参与者）的操作结果并最终指示这些节点是否要把操作结果进行真正的提交（比如将更新后的数据写入磁盘等等）。因此，二阶段提交的算法思路可以概括为：参与者将操作成败通知协调者，再由协调者根据所有参与者的反馈情报决定各参与者是否要提交操作还是中止操作。需要注意的是，二阶段提交（英語：2PC）不应该与并发控制中的二阶段锁（英語：2PL）混淆。 Commit-Protokolle regeln die Festschreibung (Commit) von Daten, die durch eine (verteilte) Transaktion beispielsweise in einem Datenbankmanagementsystem verändert werden sollen. 2相コミット（Two-Phase Commit）とは、コンピュータネットワークやデータベースにおいて、分散システム内の全ノードがトランザクションのコミットに合意するための分散アルゴリズムあるいはプロトコルである。ネットワーク障害やノード故障の場合も考慮され、結果としてトランザクションはコミットが成功するか失敗するかのいずれかの状態となる。しかし、Dale Skeen とマイケル・ストーンブレーカーの研究によれば、2相コミットは同時に複数のサイトが（無作為に）障害に陥った場合に対応できない。このアルゴリズムの2相とは、「調整者; coordinator」が全「参加者; cohorts」の調整を行う「コミット要求相; commit-request phase」と、調整者の決定によって全参加者がトランザクションを完了させる「コミット相; commit phase」である。 El protocolo de consolidación en dos fases, confirmación en dos fases o commit en dos fases, también conocido por las siglas 2PC (del inglés 2-phase commit), es un protocolo de consenso distribuido que permite a todos los nodos de un sistema distribuido ponerse de acuerdo para consolidar a una transacción. Típicamente es usado en bases de datos distribuidas. El objetivo del protocolo es que todos los nodos realicen un commit de la transacción o la aborten.
dcterms:subject: dbc:Data_management dbc:Transaction_processing
dbo:wikiPageID: 787850
dbo:wikiPageRevisionID: 1078983413
dbo:wikiPageWikiLink: dbr:Three-phase_commit_protocol dbr:Server_log dbr:Distributed_algorithm dbr:Two_Generals'_Problem dbr:Stable_storage dbr:Commit_(data_management) n14:Open_XA dbr:Concurrency_control dbr:The_Open_Group dbr:Raft_(algorithm) dbr:Two-phase_locking dbr:Database dbr:Redo_log dbr:Computer_network dbc:Data_management dbr:Transaction_processing dbr:Transaction_manager dbc:Transaction_processing dbr:Atomic_commit dbr:Distributed_transaction dbr:Computer_networking dbr:Consensus_(computer_science) dbr:Write_ahead_logging dbr:Paxos_algorithm dbr:Tree_(data_structure) dbr:Recovery_procedure
owl:sameAs: n7:9iX3 dbpedia-it:Protocollo_di_aggiornamento_a_due_fasi dbpedia-hu:Kétfázisú_tranzakció-jóváhagyás dbpedia-da:Two-phase_commit dbpedia-es:Commit_de_dos_fases dbpedia-vi:Xác_nhận_hai_pha_(khoa_học_máy_tính) dbpedia-ko:2단계_커밋_프로토콜 dbpedia-de:Commit-Protokoll dbpedia-zh:二阶段提交 wikidata:Q1067690 dbpedia-uk:Двофазна_транзакція yago-res:Two-phase_commit_protocol dbpedia-ja:2相コミット freebase:m.03c7r7
dbp:wikiPageUsesTemplate: dbt:Redirect dbt:Reflist
dbo:abstract: Nelle reti di calcolatori e nei database, il protocollo di aggiornamento a due fasi (conosciuto come 2PC - Two-phase commit protocol) è un algoritmo distribuito che comprende tutti i nodi in un sistema distribuito per convalidare una transazione. Il protocollo deriva da tutti i nodi che convalidano la transazione o la fanno abortire, anche nel caso di errori di rete o dovuti ai nodi. Comunque sia, in base al lavoro svolto da Skeen e Stonebraker, il protocollo non gestirà più di un errore alla volta. Le due fasi dell'algoritmo sono la fase di richiesta di validazione, nella quale il coordinatore si occupa di preparare tutti i gruppi e richiedere una convalida, e la fase di validazione, nella quale il coordinatore completa la transazione a tutti i gruppi. Sin dagli anni '80, la tecnologia di aggiornamento a due fasi è stata usata per il controllo automatico, per monitorare le validazioni e/o il ripristino delle attività riguardanti le transazioni in un sistema di database distribuito. Questa tecnologia viene impiegata quando gli aggiornamenti dei dati necessitano di avvenire simultaneamente in database multipli all'interno di un sistema distribuito. Nei sistemi di database distribuiti gli aggiornamenti a due fasi sono pensati per garantire l'integrità e l'accuratezza dei dati attraverso blocchi sincronizzati di ogni parte di una transazione. Risulta particolarmente utile per le prenotazioni di hotel e aerei, transazioni di merci, transazioni bancarie e per le carte di credito. In transaction processing, databases, and computer networking, the two-phase commit protocol (2PC) is a type of atomic commitment protocol (ACP). It is a distributed algorithm that coordinates all the processes that participate in a distributed atomic transaction on whether to commit or abort (roll back) the transaction. This protocol (a specialised type of consensus protocol) achieves its goal even in many cases of temporary system failure (involving either process, network node, communication, etc. failures), and is thus widely used.However, it is not resilient to all possible failure configurations, and in rare cases, manual intervention is needed to remedy an outcome. To accommodate recovery from failure (automatic in most cases) the protocol's participants use logging of the protocol's states. Log records, which are typically slow to generate but survive failures, are used by the protocol's recovery procedures. Many protocol variants exist that primarily differ in logging strategies and recovery mechanisms. Though usually intended to be used infrequently, recovery procedures compose a substantial portion of the protocol, due to many possible failure scenarios to be considered and supported by the protocol. In a "normal execution" of any single distributed transaction (i.e., when no failure occurs, which is typically the most frequent situation), the protocol consists of two phases: 1. * The commit-request phase (or voting phase), in which a coordinator process attempts to prepare all the transaction's participating processes (named participants, cohorts, or workers) to take the necessary steps for either committing or aborting the transaction and to vote, either "Yes": commit (if the transaction participant's local portion execution has ended properly), or "No": abort (if a problem has been detected with the local portion), and 2. * The commit phase, in which, based on voting of the participants, the coordinator decides whether to commit (only if all have voted "Yes") or abort the transaction (otherwise), and notifies the result to all the participants. The participants then follow with the needed actions (commit or abort) with their local transactional resources (also called recoverable resources; e.g., database data) and their respective portions in the transaction's other output (if applicable). The two-phase commit (2PC) protocol should not be confused with the two-phase locking (2PL) protocol, a concurrency control protocol. El protocolo de consolidación en dos fases, confirmación en dos fases o commit en dos fases, también conocido por las siglas 2PC (del inglés 2-phase commit), es un protocolo de consenso distribuido que permite a todos los nodos de un sistema distribuido ponerse de acuerdo para consolidar a una transacción. Típicamente es usado en bases de datos distribuidas. El objetivo del protocolo es que todos los nodos realicen un commit de la transacción o la aborten. Las dos fases del algoritmo son la «fase de petición de commit», en el cual el coordinador intenta preparar a todos los demás, y la «fase de commit» o consolidación, en la cual el coordinador completa las transacciones a todos los demás participantes. 트랜잭션 처리, 데이터베이스, 컴퓨터 네트워크에서 2단계 커밋 프로토콜(two-phase commit protocol, 2PC)은 원자적 커밋 프로토콜(ACP)의 일종이다. 트랜잭션을 커밋할지, 아니면 롤백할지에 대해 분산 원자적 트랜잭션에 관여하는 분산 알고리즘의 하나이다. (특별한 종류의 ) 이 프로토콜은 수많은 종류의 일시적 시스템 문제(프로세스, 네트워크 노드, 통신 등)에도 목표를 수행하므로 널리 이용된다. 그러나 잠재적인 모든 문제 구성을 복구할 수 있는 것은 아니며, 드문 경우 문제 해결을 위해 사용자(시스템의 관리자)의 간섭이 요구된다. 二阶段提交（英語：Two-phase Commit）是指在计算机网络以及数据库领域内，为了使基于分布式系统架构下的所有节点在进行事务提交时保持一致性而设计的一种演算法。通常，二阶段提交也被称为是一种协议（Protocol）。在分布式系统中，每个节点虽然可以知晓自己的操作时成功或者失败，却无法知道其他节点的操作的成功或失败。当一个事务跨越多个节点时，为了保持事务的ACID特性，需要引入一个作为协调者的组件来统一掌控所有节点（称作参与者）的操作结果并最终指示这些节点是否要把操作结果进行真正的提交（比如将更新后的数据写入磁盘等等）。因此，二阶段提交的算法思路可以概括为：参与者将操作成败通知协调者，再由协调者根据所有参与者的反馈情报决定各参与者是否要提交操作还是中止操作。需要注意的是，二阶段提交（英語：2PC）不应该与并发控制中的二阶段锁（英語：2PL）混淆。 Двофазна транзакція — патерн проєктування, який дозволяє координувати транзакції здійснені до різних баз даних у вигляді однієї операції. 2相コミット（Two-Phase Commit）とは、コンピュータネットワークやデータベースにおいて、分散システム内の全ノードがトランザクションのコミットに合意するための分散アルゴリズムあるいはプロトコルである。ネットワーク障害やノード故障の場合も考慮され、結果としてトランザクションはコミットが成功するか失敗するかのいずれかの状態となる。しかし、Dale Skeen とマイケル・ストーンブレーカーの研究によれば、2相コミットは同時に複数のサイトが（無作為に）障害に陥った場合に対応できない。このアルゴリズムの2相とは、「調整者; coordinator」が全「参加者; cohorts」の調整を行う「コミット要求相; commit-request phase」と、調整者の決定によって全参加者がトランザクションを完了させる「コミット相; commit phase」である。 Commit-Protokolle regeln die Festschreibung (Commit) von Daten, die durch eine (verteilte) Transaktion beispielsweise in einem Datenbankmanagementsystem verändert werden sollen.
gold:hypernym: dbr:Protocol
prov:wasDerivedFrom: wikipedia-en:Two-phase_commit_protocol?oldid=1078983413&ns=0
dbo:wikiPageLength: 14030
foaf:isPrimaryTopicOf: wikipedia-en:Two-phase_commit_protocol

Subject Item: dbr:Serializability
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol

Subject Item: dbr:Two-phase-commit_protocol
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageRedirects: dbr:Two-phase_commit_protocol

Subject Item: dbr:Two-phase_commit
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageRedirects: dbr:Two-phase_commit_protocol

Subject Item: dbr:Two_phase_commit
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageRedirects: dbr:Two-phase_commit_protocol

Subject Item: dbr:2-phase_commit
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageRedirects: dbr:Two-phase_commit_protocol

Subject Item: dbr:2PC
dbo:wikiPageWikiLink: dbr:Two-phase_commit_protocol
dbo:wikiPageRedirects: dbr:Two-phase_commit_protocol

Subject Item: wikipedia-en:Two-phase_commit_protocol
foaf:primaryTopic: dbr:Two-phase_commit_protocol