Increasing Data TLB Resilience to Transient Errors

2005 ◽  
Author(s):  
Feihui Li ◽  
M. Kandemir
Keyword(s):  
Transient Errors

Evaluating instruction cache vulnerability to transient errors

2007 ◽  
Vol 35 (4) ◽  
pp. 21-28 ◽  
Author(s):  
Jun Yan ◽  
Wei Zhang
Keyword(s):  
Instruction Cache ◽  
Transient Errors

scholarly journals Lost in transcription: transient errors in information transfer

2015 ◽  
Vol 24 ◽  
pp. 80-87 ◽  
Author(s):  
Alasdair JE Gordon ◽  
Dominik Satory ◽  
Jennifer A Halliday ◽  
Christophe Herman
Keyword(s):  
Information Transfer ◽  
Transient Errors

scholarly journals Analyzing Radiation-Induced Transient Errors on SRAM-Based FPGAs by Propagation of Broadening Effect

IEEE Access ◽  
2019 ◽  
Vol 7 ◽  
pp. 140182-140189 ◽  
Author(s):  
Corrado De Sio ◽  
Sarah Azimi ◽  
Luca Sterpone ◽  
Boyang Du
Keyword(s):  
Transient Errors ◽  
Radiation Induced

scholarly journals Understanding the evolution of conditions data access through Frontier for the ATLAS Experiment

2019 ◽  
Vol 214 ◽  
pp. 03020
Author(s):  
Michal Svatos ◽  
Alessandro De Salvo ◽  
Alastair Dewhurst ◽  
Emmanouil Vamvakopoulos ◽  
Julio Lozano Bahilo ◽  
...  
Keyword(s):  
Distributed Computing ◽  
Monitoring System ◽  
Data Access ◽  
Computing System ◽  
High Load ◽  
Cascading Failure ◽  
Cascading Failures ◽  
Atlas Experiment ◽  
Transient Errors ◽  
Increasing Demand

The ATLAS Distributed Computing system uses the Frontier system to access the Conditions, Trigger, and Geometry database data stored in the Oracle Offline Database at CERN by means of the HTTP protocol. All ATLAS computing sites use Squid web proxies to cache the data, greatly reducing the load on the Frontier servers and the databases. One feature of the Frontier client is that in the event of failure, it retries with different services. While this allows transient errors and scheduled maintenance to happen transparently, it does open the system up to cascading failures if the load is high enough. Throughout LHC Run 2 there has been an ever increasing demand on the Frontier service. There have been multiple incidents where parts of the service failed due to high load. A significant improvement in the monitoring of the Frontier service wasrequired. The monitoring was needed to identify both problematic tasks, which could then be killed or throttled, and to identify failing site services as the consequence of a cascading failure is much higher. This presentation describes the implementation and features of the monitoring system.

Sign in / Sign up

Export Citation Format

Share Document