MétaCan
Menu
Back to cohort

A Fault Detection Mechanism for Database Management Systems on Mobile Edge Computing

2023· article· en· W4386280474 on OpenAlexfundno aff
Fotios Voutsas, John Violos, Aris Leivadeas

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsnot available
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceTestbedGeneralityDatabaseEnhanced Data Rates for GSM EvolutionAnomaly detectionContext (archaeology)Edge computingData miningDistributed computingComputer networkArtificial intelligence

Abstract

fetched live from OpenAlex

The ever-increasing demand for reliable data storage solutions at mobile edge computing makes it a necessity to develop timely fault detection mechanisms. In this paper, we address the research challenge of detecting failed data queries in an application and infrastructure agnostic way. In this context, the mobile edge infrastructure includes a Database Management System (DBMS) that runs on server nodes and client nodes that retrieve, store, update and delete data in the DBMS. Specifically, we propose a rule-based algorithm with thresholds that takes as input utilization metrics and detects the faults. It does so without using sensitive DBMS credentials. To verify the applicability and the generality of the proposed algorithm, we made an experimental evaluation with six different query generation functions and testbed configurations. The comparison with other popular machine learning methods used for anomaly detection in monitoring systems, showed that the proposed algorithm significantly surpasses the other methods in terms of Precision and F1-score. During the operation of the mobile edge computing we gathered the utilization metrics, the queries success and fail status and created six datasets that we make them publicly available.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.011
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.003
Threshold uncertainty score0.018

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.011
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0030.001
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0030.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0010.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.030
GPT teacher head0.273
Teacher spread0.243 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicIoT and Edge/Fog ComputingFrench-language works237,207