- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Server error after someone change config
- Labels:
-
Apache Hadoop
Created on ‎04-13-2015 04:31 PM - edited ‎09-16-2022 02:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What can I check to resolve this issue? Had someone changing stuff and have no idea what they did to kill my hadoop cloudera.
15/04/13 16:28:18 INFO mapred.FileInputFormat: Total input paths to process : 10
15/04/13 16:28:18 INFO mapred.JobClient: Running job: job_201504131620_0001
15/04/13 16:28:19 INFO mapred.JobClient: map 0% reduce 0%
15/04/13 16:28:22 INFO mapred.JobClient: Task Id : attempt_201504131620_0001_m_000011_0, Status : FAILED
java.lang.Throwable: Child Error
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:250)
Caused by: java.io.IOException: Task process exit with nonzero status of 2.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:237)
Created ‎04-30-2015 09:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just did a roll back which resolved the issue. We have been testing apache hadoop as well so that's why I was delayed to answer.
Thanks
Created ‎04-29-2015 08:04 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you had any luck with this?
Created ‎04-30-2015 07:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If there was some changes to the MapReduce or Yarn service, you can see those configuration changes by hitting the "History and Rollback" button on the configuration page for the service. That will display the most recent changes, and you can review those and rollback if needed.
Created ‎04-30-2015 09:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just did a roll back which resolved the issue. We have been testing apache hadoop as well so that's why I was delayed to answer.
Thanks
