Hi I was running WALPlayer that output HFile for future bulkload. There are 6200 hlogs, and the total size is about 400G.
The mapreduce job finished. But I saw two bad things: 1. More than half of RS died. I checked the syslog, it seems they are killed by OOM. They also have very high CPU spike for the whole time during WALPlayer cpu user usage of 84.4% matches resource limit [cpu user usage>70.0%] 2. Mapreduce job also has failure of Java heap Space error. My job set the heap usage as 2G, *mapred.child.java.opts*-Xmx2048m Does this mean WALPlayer cannot support this load on this kind of setting? Thanks Tian-Ying
