Alejandro Abdelnur 2013-06-20, 15:31
Arun C Murthy 2013-06-20, 21:40
Roman Shaposhnik 2013-06-20, 05:02
Todd Lipcon 2013-06-20, 06:10
Suresh Srinivas 2013-06-20, 05:16
Arun C Murthy 2013-06-19, 06:58
Devaraj k 2013-06-19, 13:13
Suresh Srinivas 2013-06-21, 01:05
I still need to look at hadoop-env.sh.
I suspect this is due to not passing Xms (starting java heap size) set to same value as Xmx (max java heap size). The recent inode id changes create hash apps based on max heap size and I have seen this problem without Xms.
Sent from a mobile device
On Jun 20, 2013, at 5:33 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
> ||| Did you change the java version? Can you please provide the JVM
> ||| configuration from hadoop-env.sh?
> Nope I didn't. In fact since Bigtop uses clean VMs every single time
> it runs tests there's also no chance of env. contamination. As far
> as the version of JVM it is still the same as I used for Bigtop 0.6.0
> (Hadoop 2.0.5 based) which is Orcale's JDK jdk1.6.0_21