A prototype for the evolution of ATLAS EventIndex based on Apache Kudu storage

The ATLAS EventIndex has been in operation since the beginning of LHC Run 2 in 2015. Like all software projects, its components have been constantly evolving and improving in performance. The main data store in Hadoop, based on MapFiles and HBase, can work for the rest of Run 2 but new solutions are...

Descripción completa

Detalles Bibliográficos
Autores principales: Baranowski, Zbigniew, Canali, Luca, Fernandez Casani, Alvaro, Gallas, Elizabeth, Garcia Montoro, Carlos, Gonzalez de la Hoz, Santiago, Hrivnac, Julius, Prokoshin, Fedor, Rybkin, Grigori, Salt, José, Sánchez, Javier, Barberis, Dario
Lenguaje:eng
Publicado: 2018
Materias:
Particle Physics - Experiment
Acceso en línea:https://dx.doi.org/10.1051/epjconf/201921404057
http://cds.cern.ch/record/2649940
Descripción
Sumario:The ATLAS EventIndex has been in operation since the beginning of LHC Run 2 in 2015. Like all software projects, its components have been constantly evolving and improving in performance. The main data store in Hadoop, based on MapFiles and HBase, can work for the rest of Run 2 but new solutions are explored for the future. Kudu offers an interesting environment, with a mixture of BigData and relational database features, which look promising at the design level. This environment is used to build a prototype to measure the scaling capabilities as functions of data input rates, total data volumes and data query and retrieval rates. In this proceedings we report on the selected data schemas and on the current performance measurements with the Kudu prototype.

Ejemplares similares