Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Im working a new project,

Im currently deciding between

flume & scribe for messaging systems... ( most probably sent to logs or hadoop )

I cannot lose a message ever.. What are your thoughts on which is better? Configuration/reliablity/adminitration wise.

If you have used / administrated both is also quite relative to answering my question.. :D


share|improve this question
relative or relevant? – Jed Daniels Nov 11 '10 at 2:55
up vote 1 down vote accepted

By far Flume is a better alternative..

Flume is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log data..

Flume provides

  • Continuous, high-performance, scalability
  • Reliable data loading and data flow monitoring from feeds
  • Logging directly to HDFS securely (made for hadoop)
  • Flexible reliability across the messaging system ( never lose a message )
  • Multiple source/collection types ( running on a port / logging from Apache / Syslog securely )
  • Robust and fault tolerant with tunable reliability mechanisms
  • Failover and recovery mechanisms

Scribe provides "somewhat" reliability, but not as comprehensive or flexible. secondly its compilation and usability is difficult in comparison to flume..

Hope this Helps :D

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.