There are two types of transactions in robotic environments: local and global. Local transactions deal with a local team of robots, while global transactions deal with coordinating all robot teams across the entire global environment. Transactions must be synchronized both within local robot teams and across global teams. Transaction managers ensure this synchronization. Transactions can be retriable, compensatable, or pivot. Retriable transactions can commit after multiple retries. Compensatable transactions can be replaced by another transaction achieving the same goal if the original fails repeatedly. Pivot transactions are neither retriable nor compensatable and cannot proceed if failed.
There are two types of transactions in robotic environments: local and global. Local transactions deal with a local team of robots, while global transactions deal with coordinating all robot teams across the entire global environment. Transactions must be synchronized both within local robot teams and across global teams. Transaction managers ensure this synchronization. Transactions can be retriable, compensatable, or pivot. Retriable transactions can commit after multiple retries. Compensatable transactions can be replaced by another transaction achieving the same goal if the original fails repeatedly. Pivot transactions are neither retriable nor compensatable and cannot proceed if failed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
There are two types of transactions in robotic environments: local and global. Local transactions deal with a local team of robots, while global transactions deal with coordinating all robot teams across the entire global environment. Transactions must be synchronized both within local robot teams and across global teams. Transaction managers ensure this synchronization. Transactions can be retriable, compensatable, or pivot. Retriable transactions can commit after multiple retries. Compensatable transactions can be replaced by another transaction achieving the same goal if the original fails repeatedly. Pivot transactions are neither retriable nor compensatable and cannot proceed if failed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
There are two types of transactions in robotic environment.
1. Local transactions: For example it deals with local team of robots
2. Global transactions: it deals with the entire global environments, all the teams in our environment. Condition: • There should be synchronization of transactions , that are executing concurrently with in a local site(i.e synchronization within a team of robots) • As well as the synchronization of transactions with global transactions running simultaneously at same or different sites.(i.e synchronization between all the teams in entire global environment) Transaction manager will be taking care of these conditions. Types of transactions • Retriable • Pivot • Compensatable Retriable: transaction ti is said to be retriable, if it is guaranteed to commit after a finite number of submissions when executed from any consistent database state. I.e even if transaction fails, it can be retried again and again, for certain times until it succeeds. Based on the Battery life available for a robot, even if the transaction gets aborted it can be retried again and again. Compensatable: Consider a transaction ti , it is retried again and again, but it doesn’t succeeds, we should select another transaction cti, that can commit successfully with the same characteristics as ti. Then we say cti is compensating for ti. ,such an transaction cti is called compensatable transaction. For example if working of an robot is failed, then a compensating robot with same characteristics (performance) and battery life can be replaced instead of that robot. For example: Transaction t1 is aborted in middle, so to compensate that ct1 is does the task and commits. If in the middle T1 restores and commits. Then ct1 will backtracks and rollbacks the commits, because t1 is working now.
Pivot: A transaction ti is said to be a pivot sub transaction, if it is neither
retriable nor compensatable. In our environment, if the robot is completely worn and no compensating robots for that task, that transaction can never take place. So the transaction is a pivot one.