On Wed, Jun 6, 2012 at 2:20 AM, Amandeep Khurana <[email protected]> wrote: >> These are general recommendations and definitely change based on the >> access patterns and the way you will be using HBase and MapReduce. In >> general, if you are building a latency sensitive application on top of >> HBase, running a MapReduce job at the same time will impact performance due >> to I/O contention. If your main access patterns is going to be running >> MapReduce over HBase tables, you should absolutely consider collocating the >> two frameworks.
Perhaps this exact point can be made (more clearly?) in the referenced Cloudera documentation? Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
