Search Analytics with Flume and HBase
•Download as ODP, PDF•
32 likes•6,885 views
This document summarizes an architecture for collecting and analyzing search analytics data using Flume and HBase. It describes: 1) Collecting search log data from applications using Flume agents and sending it to a Flume collector. 2) The Flume collector processes the log messages and sends them to an "raw logs" table in HBase using a Flume HBase sink. 3) The data in HBase is later processed by MapReduce jobs to generate search analytics reports and metrics that are displayed on a reporting web application.
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (14)
Viewers also liked
Viewers also liked (20)
Similar to Search Analytics with Flume and HBase
Similar to Search Analytics with Flume and HBase (20)
More from Sematext Group, Inc.
More from Sematext Group, Inc. (20)
Recently uploaded
Recently uploaded (20)
Search Analytics with Flume and HBase
- 1. Search Analytics with Flume & HBase Otis Gospodneti ć ••• Sematext International
- 3. What Why How
- 5. Role of Flume and HBase + Flume HBase Sink
- 6. Challenges
- 8. Lucene in Action 1 & 2 co-author
- 9. Lucene Consulting since 2005
- 10. Sematext Int'l since 2007
- 12. Search (Lucene, Solr, Elastic Search...)
- 13. Web Crawling (Nutch)
- 14. Machine Learning (Mahout)
- 17. Comparisons of time periods
- 18. Top N reports
- 20. Report Example
- 22. Want to know how their search is behaving
- 23. … subliminal msg: go use this site
- 25. Metric Capture Web App
- 29. Search Analytics Reporting Web App
- 32. Centrally manageable, open source
- 33. Agents get data from app, Collectors save it
- 34. Abstractions: Source -> Decorator(s) -> Sink
- 36. On top of HDFS
- 37. MapReducable
- 39. Architecture #1
- 40. Architecture #1 - Getting Messy
- 41. Arch #2 – HBaseLog4JAppender
- 43. e.g. changing sampling rate
- 44. Architecture #3 – Flume OOTB
- 45. Arch #4 – Flume HBase Sink
- 47. Reviewed, pending commit
- 48. Similar to FLUME-6 (basic example), but more flexible
- 51. User actions start getting logged to a log file
- 52. Configure Flume Agent to "tail" the generated logs and send data to Flume Collector
- 53. Collector processes log messages and sends them to HBase's "raw logs" table
- 57. Good community, good progress
- 58. But: more complex, more moving parts
- 59. On Flume: slideshare.net/cloudera/inside-flume
- 62. Scalable aggregate data storage
- 63. Fast scans for time ranges, fast key lookups
- 64. Easy storage and compute power expansion
- 65. Good looking roadmap, community, progress
- 69. Work @ Sematext We are hiring world-wide! Search & Data Analytics Machine Learning & NLP Biiig Data
- 72. @ sematext
- 73. @ otisg
Editor's Notes
- 10 days of data (5K/min)
- Flume is used simply to collect logs to a central place (HDFS) from multiple agents. But at the end we still have a single log file that something (raw log importer) then needs to process. No HBase is involved directly with Flume here and there is no HBase sink in this scenario.
- Making use of Flume's ability to plug in different Sinks, so instead of just collecting data to a log file on HDFS, we hook up FLUME-247 Sink to Flume and make it write directly to HBase.
- 2h, 2K/min, 1sys (240K actions, 43mb of input data) 1193mb - no prune, no compress 624mb - prune sort index only, no compress 408mb - prune, no compress 196mb - no prune, copress 106mb - prune sort index only, compress 64mb - prune, compress