Unreliable failure detectors Sample Clauses

Unreliable failure detectors. The failure detector concept was introduced by Xxxxxxx and Xxxxx in [15] with the purpose of identifying the minimal extensions to an asynchronous system that would render consensus solvable. In [15], the authors identify two completeness properties and four accuracy properties. This classification leads to eight classes of failure detectors, which can be reduced to just four distinct classes, by applying reduction algorithms. In the following, we provide some basic definitions for the two completeness and four ac- curacy properties. The weak completeness property requires that there is a time after which ev- ery process that crashes is permanently suspected by some correct process. If we strengthen the constraint and we require that eventually every crashed process is permanently sus- pected by every correct process, we obtain the so-called strong completeness property. The perpetual accuracy property requires that accuracy is always satisfied. Eventual accu- racy relaxes this constraint: accuracy must be permanently satisfied only after some time. Strong accuracy states that no process is suspected before it crashes. The less constraint-full version of strong accuracy is weak accuracy: some correct process is never suspected. Among the classes of failure detectors, we particularly focus on three of them, which are relevant for our work, namely Eventually Weak, denoted by ♢W, Perfect, denoted by P, and Eventually Strong, denoted by ♢S. The Eventually Weak class of failure detectors is described in [15] as the weakest class that renders consensus solvable. A failure detector is in ♢W if it satisfies weak completeness and eventual weak accuracy. These two properties require that eventually some conditions are satisfied and hold forever. However, in a real system in which properties cannot be satisfied forever, it is required that they hold for a sufficiently long period of time. If we refer to the consensus problem, we can quantify the “sufficiently long” period of time as being long enough to allow the algorithm to terminate and each process to decide. The Perfect class, denoted by P, contains the failure detectors that satisfy the most constraint-full requirements, which are strong completeness and strong accuracy. Another important class of failure detectors, intensively investigated in the literature, is the class of Eventually Strong failure detectors, denoted by ♢S. A failure detector belonging to this class satisfies the properties of strong complete...
Sample 1

Related to Unreliable failure detectors

  • Smoke Detectors At Owner's expense, smoke detectors will be installed on the Property in working condition in accordance with the law prior to the tenant's occupancy. During the occupancy, it shall be the tenant's responsibility to maintain all smoke detectors. Owner will replace smoke detector equipment as needed.

  • Epidemic Failure Warranty Supplier warrants all Products against Epidemic Failure for a period of three years after DXC’s Acceptance. Epidemic Failure means the occurrence of the same failure, defect, or non-conformity with an Order in 2% or more of Products within any three-month period.

  • Epidemic Failure “Epidemic Failure” for any particular Product shall mean a failure resulting from defects in material, workmanship, and manufacturing process, including but not limited to the use of Components with known defects. The Epidemic Failure clause shall be invoked [***]. The failure rate may be calculated [***], as determined by BUYER. Epidemic failures do not supersede the requirements of any expressed or implied warranty defined herein. In the case of an epidemic failure, SUPPLIER’s obligation is to propose an action plan to fix the failure of any affected Product within seventy-two (72) hours of discovery. SUPPLIER shall implement this action plan upon BUYER’s acceptance thereof. If the action plan is not acceptable to BUYER, BUYER can require SUPPLIER to repair or replace, at BUYER’s option, the affected Product. In addition to bearing the costs associated therewith, if requested by BUYER, SUPPLIER shall support and provide at SUPPLIER’s expense a sufficient number of units of the Product to permit the field exchange or “hot swap” of Products at customer sites. The parties agree to make all reasonable efforts to complete the repair or replacement of all affected Products within eight (8) Business Days after written notice of epidemic failure by BUYER to SUPPLIER. SUPPLIER also agrees that BUYER will be supported with accelerated shipments of replacement Product to cover BUYER’s supply requirements. If an Epidemic Failure is caused by (i) a design, including a BUYER-provided test process, as required by the Specifications or (ii) a failure by a Component required by the Specifications, (iii) misuse or damage during transit or damage by a third party at no fault of SUPPLIER, SUPPLIER shall perform the obligations in this Section 10.5 and BUYER shall pay to SUPPLIER the fees mutually agreed upon by the parties in writing. If an Epidemic Failure is caused by any other reason other than as set forth in the immediately preceding sentence, SUPPLIER shall perform the obligations set forth in this Section free of charge. Confidential treatment is being requested for portions of this document. This copy of the document filed as an exhibit omits the confidential information subject to the confidentiality request. Omissions are designated by the symbol [***]. A complete version of this document has been filed separately with the Securities and Exchange Commission.

  • Epidemic Failure Remedy If an Epidemic Failure occurs, all costs, including but not limited to, replacement Products, parts, upgrades, materials, labor, transportation and inventory replacement arising from an Epidemic Failure shall be borne by Supplier, regardless of whether DXC initiates a field stocking recall or customer-based recall or retrofit, including Products in distributor inventory and DXC’s installed base. Supplier, at its expense, will ensure that such Products, parts or upgrades have the highest shipping priority. DXC reserves the right to procure, upon terms it deems appropriate, similar products to substitute the affected Products, and Supplier shall promptly reimburse DXC for all costs, charges, prices and fees paid in purchasing the substitute products.

  • Intrusion Detection All systems involved in accessing, holding, transporting, and protecting DHCS PHI or PI that are accessible via the Internet must be protected by a comprehensive intrusion detection and prevention solution.

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Payment Failure Any Credit Party (i) fails to pay any principal when due under this Agreement or (ii) fails to pay, within three Business Days of when due, any other amount due under this Agreement or any other Credit Document, including payments of interest, fees, reimbursements, and indemnifications;

  • Power Failure Power Failure means the failure of power or other utility service if the failure takes place off the "residence premises". But if the failure results in a loss, from a Peril Insured Against on the "residence premises", we will pay for the loss caused by that peril.

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.