AnsweredAssumed Answered

Tasktracker fails to resolve own ipaddress?

Question asked by andrew_wells on Jul 20, 2011
Latest reply on Jul 21, 2011 by srivas
I have successfully brought up a 2 node cluster so far, but I am now running into this issue with the tasktracker. I believe the error causing this was found in the log: <tt>/opt/mapr/logs/maprcli-root-0.log</tt>
<pre>
Header: hostName: conf2.example.com, Time Zone: Eastern Standard Time, processName: MapRCLI, processId: 357
2011-07-21 10:37:33,017 INFO  com.mapr.cliframework.driver.CLIMainDriver [main]: [volume, create, -name, mapr.conf2.example.com.local.mapred, -localvolumehost, conf2.example.com, -localvolumeport, 5660, -shufflevolume, true, -rereplicationtimeoutsec, 300, -replication, 1]
2011-07-21 10:37:33,069 ERROR com.mapr.cli.VolumeCommands volumeCreate [main]: Volume create: Unable to determine ipaddress of host conf2.example.com during volume create of mapr.conf2.example.com.local.mapred
2011-07-21 10:37:33,071 INFO  com.mapr.cliframework.driver.CLIMainDriver [main]: ERROR (22) -  Unable to determine ipaddress of conf2.example.com while creating volume mapr.conf2.example.com.local.mapred
</pre>

Any hints on what this means? And it is just the tasktracker service that is affected, it attaches to the cldb fine, and provides disk space to the HDFS(maprfs).

Outcomes