Changes between Version 1 and Version 2 of PDAD_Applications

Jan 14, 2010, 1:51:32 AM (14 years ago)



  • PDAD_Applications

    v1 v2  
    11= Applications =
    3 [available/unavailable se refera probabil la tipul resursei care a generat fault-ul (eg cpu availability 60% sau o resursa unavailable)]
     3We decided to do several application in the realm of statistics on large amount of data, keeping in mind to choose them as different as possible so as to make the comparison more relevant. As a result, we chose some real world data, available online at [ INRIA Failure Trace Archive], having as an advantage the fact that data is structured and we could test the applications on various input sizes, from tens on MB to tens of GB. This data archive presents facts about job failures and the tales of interest for out applications are event_trace (a trace of events that failed), node (identifies nodes on which the jobs ran), component (describes component codes), event_trace.event_end_reason code. A full description of these tables is available at the link mentioned earlier.
    5  * care dintre motivele de fault apare cel mai des in event-uri event_trace.event_end_reason - claudiu
    6  * care este durata medie a event-urilor - cristina
    7    * MapReduce DONE
    8    * Pig DONE
    9  * ce componenta apare cel mai des in fault event-uri component.component_type code - claudiu
    10  * avand event-urile impartite pe categorii dupa durata, care este cauza de fault cea mai intalnita pe fiecare categ event_trace.event_end_reason - cristina [-> sch in enumerarea pe fiecare categ a numarului de joburi terminate din fiecare cauza frecventa (>1000 failed)]
    11    * MapReduce DONE
    12    * Pig DONE
    13  * pt fiecare categ din event_trace.event_end_reason code ranges, care dintre event_trace.event_end_reason code definitions apare cel mai des (numarul de dati cat apare fiecare..) - claudiu
    14  * in ce locatie geografica sunt nodurile pe care se inregistreaza cele mai multe failure-uri (node_location luat uitandu-ne dupa node_id din event_trace) - cristina
    15    * MapReduce DONE
    16    * Pig DONE
     6Below there is a short description of each application:
     7 a. Which one of the fault reasons is the most frequent? This application uses the event_trace table, looking at event_end_reason column
     8 b. Which is the medium duration for events? This application uses the event_trace table, looking at event_start_time and event_end_time columns
     9 c. Which component is the most frequent as a fault cause? This application uses the event_trace table, using the component_id column and also the table component table, looking at component_type column
     10 d. Having a classification for job duration as short, medium and long, find out the most frequent (>1000) causes of failures for each of these categories. It uses event_trace table, looking at event_start_time and event_end_time columns and also event_trace.event_end_reason code table.
     11 e. For each category from event_trace.event_end_reason code ranges, which of event_trace.event_end_reason code definitions is the most frequent?
     12 f. Number of failures for each geographical location. This application uses
     16and the approach used for each of the three mediums.
    1821Obs: pt Pig, comment-urile din input, desi nu afecteaza functionarea script-ului, nu sunt ignorate iar rezultatele ce implica un COUNT (precum media) nu vor fi corecte