- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
End of File Exception between local host is: "02.app.test.foo.net/172.16.13.50"; destination host is: "06.app.test.foo.net":41450; : java.io.EOFException; For more details see: http://wiki.apache.org/hadoop/EOFException
- Labels:
-
Apache Hadoop
-
Apache Pig
-
Apache Tez
Created 01-29-2019 03:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I submitted the pig script by passing parameters and I got below end of file exception in tez. What can be solution of it?
pig -param "DATE=$DATE" -param "LOCATION=$LOCATION" -param "TABLE_LOCATION=$TABLE_LOCATION" -x tez -useHCatalog -f /lake/T/S/r11.pig
[PigTezLauncher-0] ERROR org.apache.pig.backend.hadoop.executionengine.tez.TezJob - Cannot submit DAG - Application id: application_1472313221699_4775
End of File Exception between local host is: "hostlaenapp02.app.test.foocorp.net/172.16.13.75"; destination host is: "hostldnapp06.app.test.foocorp.net":41450; : java.io.EOFException; For more details see: http://wiki.apache.org/hadoop/EOFException
Created 01-29-2019 03:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Encountering the exact issue. Did you find a solution/explanation for this? @Ashish Vishnoi
,Have you found a solution for this? Seeing the exact issue.
Created 01-29-2019 03:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The original post was edited Tue Jan 29 15:26:21 UTC 2019 to remove some sensitive information.
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Created 05-20-2021 02:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I encountered the same problem. For my case , the problem was the long length of ipc message.
I added the following to core-site and got fixed.
<property>
<name>ipc.maximum.data.length</name>
<value>134217728</value>
</property>
You also might double check name-node and data-node heap size.
Created 05-21-2021 12:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Reza77, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post.
Regards,
Vidya Sargur,Community Manager
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: