Are there specific things you are looking for, that's a lot of information
you are looking for. (I can post them all, it's just heavy). One thing I
did shift form java6 to java7, I wonder if that playing a part here.  I
can't go back either :(.  I've tried updating and recompiling my
hadoop-mesos against the version of hadoop I am using, with no luck.  Still
getting the same error. For the JT config, are you looking for the whole
mapred-site?  Thanks!



On Tue, Nov 18, 2014 at 2:32 PM, Tom Arnfeld <[email protected]> wrote:

> Hi John,
>
> Could you paste your JT configuration and the configuration that gets
> printed out by the executor?
>
> Also, what version of Hadoop are you running, and what revision of the
> framework?
>
> Cheers,
>
> Tom.
>
> --
>
> Tom Arnfeld
> Developer // DueDil
>
> (+44) 7525940046
> 25 Christopher Street, London, EC2A 2BS
>
>
> On Tue, Nov 18, 2014 at 8:27 PM, John Omernik <[email protected]> wrote:
>
>> Hey all, I updated somethings on my cluster and in broke.  :)
>>
>> That said, I am at a loss, the JT spins up, however tasks fail right
>> after the configuration listing with the error below, and am not sure how
>> to get the debug information to troubleshoot this. Any pointers would be
>> appreciated.
>>
>> Thanks!
>>
>>  14/11/18 14:19:42 INFO mapred.TaskTracker: /tmp is not tmpfs or ramfs. Java 
>> Hotspot Instrumentation will be disabled by default
>> 14/11/18 14:19:42 INFO mapred.TaskTracker: Cleaning up config files from the 
>> job history folder
>> java.lang.NumberFormatException: null
>>      at java.lang.Integer.parseInt(Integer.java:454)
>>      at java.lang.Integer.valueOf(Integer.java:582)
>>      at 
>> org.apache.hadoop.mapred.TaskTracker.getResourceInfo(TaskTracker.java:2965)
>>      at org.apache.hadoop.mapred.TaskTracker.<init>(TaskTracker.java:2108)
>>      at 
>> org.apache.hadoop.mapred.MesosExecutor.launchTask(MesosExecutor.java:80)
>> Exception in thread "Thread-1" I1118 14:19:42.040426  8716 exec.cpp:413] 
>> Deactivating the executor libprocess
>>
>>
>>
>

Reply via email to