You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Neelesh Srinivas Salian (JIRA)" <ji...@apache.org> on 2016/09/09 23:04:20 UTC

[jira] [Commented] (FLINK-1914) Wrong FS while starting YARN session without correct HADOOP_HOME

    [ https://issues.apache.org/jira/browse/FLINK-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478539#comment-15478539 ] 

Neelesh Srinivas Salian commented on FLINK-1914:
------------------------------------------------

Sounds good [~rmetzger]. Closing the JIRA.

> Wrong FS while starting YARN session without correct HADOOP_HOME
> ----------------------------------------------------------------
>
>                 Key: FLINK-1914
>                 URL: https://issues.apache.org/jira/browse/FLINK-1914
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN Client
>            Reporter: Zoltán Zvara
>            Priority: Trivial
>              Labels: yarn, yarn-client
>
> When YARN session invoked ({{yarn-session.sh}}) without a correct {{HADOOP_HOME}} (AM still deployed to - for example to {{0.0.0.0:8032}}), but the deployed AM fails with an {{IllegalArgumentException}}:
> {code}
> java.lang.IllegalArgumentException: Wrong FS: file:/home/.../flink-dist-0.9-SNAPSHOT.jar, expected: hdfs://localhost:9000
> 	at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:642)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:181)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.access$000(DistributedFileSystem.java:92)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1106)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1102)
> 	at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1102)
> 	at org.apache.flink.yarn.Utils.registerLocalResource(Utils.java:105)
> 	at org.apache.flink.yarn.ApplicationMasterActor$$anonfun$org$apache$flink$yarn$ApplicationMasterActor$$startYarnSession$2.apply(ApplicationMasterActor.scala:436)
> 	at org.apache.flink.yarn.ApplicationMasterActor$$anonfun$org$apache$flink$yarn$ApplicationMasterActor$$startYarnSession$2.apply(ApplicationMasterActor.scala:371)
> 	at scala.util.Try$.apply(Try.scala:161)
> 	at org.apache.flink.yarn.ApplicationMasterActor$class.org$apache$flink$yarn$ApplicationMasterActor$$startYarnSession(ApplicationMasterActor.scala:371)
> 	at org.apache.flink.yarn.ApplicationMasterActor$$anonfun$receiveYarnMessages$1.applyOrElse(ApplicationMasterActor.scala:155)
> 	at scala.PartialFunction$OrElse.apply(PartialFunction.scala:162)
> 	at org.apache.flink.runtime.ActorLogMessages$$anon$1.apply(ActorLogMessages.scala:37)
> 	at org.apache.flink.runtime.ActorLogMessages$$anon$1.apply(ActorLogMessages.scala:30)
> 	at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:118)
> 	at org.apache.flink.runtime.ActorLogMessages$$anon$1.applyOrElse(ActorLogMessages.scala:30)
> 	at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
> 	at org.apache.flink.runtime.jobmanager.JobManager.aroundReceive(JobManager.scala:94)
> {code}
> IMO this {{IllegalArgumentException}} should get handled in {{org.apache.flink.yarn.Utils.registerLocalResource}} or on an upper level to provide a better error message. This needs to be looked up from YARN logs at the moment, which is painful to a trivial mistake like missing {{HADOOP_HOME}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)