Logging Apache Spark How we made it easy
summary
Centralized log search for Spark on EMR uses Filebeat on every EC2 node and Metricbeat, shipping lines to Redis -> Logstash -> Elasticsearch -> Kibana via bootstrap bash scripts that install RPMs edit YAML with sed and wait for HDFS and JDK. Logs get tagged with team name flow name and EMR cluster id so queries are precise. The system surfaces over 30,000 warnings and 23 errors in dashboards, works in production, and later replaces Redis with Kafka to remove a bottleneck.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:08Nielsen's Data Architecture overview
- 2:06How we used to do it
- 4:51Solution architecture
- 5:25Solution overview
- 6:02Bootstrapping
- 9:38YAML Template File
- 10:08Installing Metricbeat
- 12:00Future and add-ons
related talks
16mLogging Apache Spark - How we made it easy
45mInteractively Analyse 100GB of Data
14mCentralized Logs using ELK (Elasticsearch, Logstash, Kibana) Stack
44mRiak, Redis, Apache Solr & Spark: Deploying with the Basho Data Platform
32mScalable Monitoring Using Prometheus with Apache Spark
11mMedic for Apache Spark - First Aid for Failing Jobs
26mFrom Spark to Elasticsearch and Back
24mCICD Pipeline and delivery of Apache Spark Applications on the cloud using AWS
