Unsubscribe
Unsubscribe - To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
Re: Could not build up connection to JobManager
Hi, Still this is no luck. I’ll upload the logs with configuration “localhost as well as “127.0.0.1” so you can take a look. 127.0.0.1 flink-Vidura-flink-client-localhost.log https://gist.github.com/viduranga/1d01149eee238158519e#file-flink-vidura-flink-client-localhost-log localhost flink-Vidura-flink-client-localhost.log https://gist.github.com/viduranga/d866c24c0ba566abab17#file-flink-vidura-flink-client-localhost-log flink-Vidura-jobmanager-localhost.log https://gist.github.com/viduranga/e7549ef818c6a2af73e9#file-flink-vidura-jobmanager-localhost-log On Mar 11, 2015, at 11:32 PM, Till Rohrmann trohrm...@apache.org wrote: Hi Dulaj, sorry for my late response. It looks as if the JobClient tries to connect to the JobManager using its IPv6 instead of IPv4. Akka is really picky when it comes to remote address. If Akka binds to the FQDN, then other ActorSystem which try to connect to it using its IP address won't be successful. I assume that this might be a problem. I tried to fix it. You can find it here [1]. Could you please try it out by starting a local cluster with the start-local.sh script. If it fails, could you please send me all log files (client, jobmanager and taskmanager). Once we figured out why the JobCilent does not connect, we can try to tackle the BlobServer issue. Cheers, Till [1] https://github.com/tillrohrmann/flink/tree/fixJobClient On Thu, Mar 5, 2015 at 4:40 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, The error message is, 21:06:01,521 WARN org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager. at org.apache.flink.client.program.Client.run(Client.java:327) at org.apache.flink.client.program.Client.run(Client.java:306) at org.apache.flink.client.program.Client.run(Client.java:300) at org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:55) at org.apache.flink.examples.java.wordcount.WordCount.main(WordCount.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:437) at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:353) at org.apache.flink.client.program.Client.run(Client.java:250) at org.apache.flink.client.CliFrontend.executeProgram(CliFrontend.java:371) at org.apache.flink.client.CliFrontend.run(CliFrontend.java:344) at org.apache.flink.client.CliFrontend.parseParameters(CliFrontend.java:1087) at org.apache.flink.client.CliFrontend.main(CliFrontend.java:1114) Caused by: java.io.IOException: JobManager at akka.tcp://flink@fe80:0:0:0:742b:7f78:fab5:68e2%11:6123/user/jobmanager not reachable. Please make sure that the JobManager is running and its port is reachable. at org.apache.flink.runtime.jobmanager.JobManager$.getJobManagerRemoteReference(JobManager.scala:957) at org.apache.flink.runtime.client.JobClient$.createJobClient(JobClient.scala:151) at org.apache.flink.runtime.client.JobClient$.createJobClientFromConfig(JobClient.scala:142) at org.apache.flink.runtime.client.JobClient$.startActorSystemAndActor(JobClient.scala:125) at org.apache.flink.runtime.client.JobClient.startActorSystemAndActor(JobClient.scala) at org.apache.flink.client.program.Client.run(Client.java:322) ... 15 more Caused by: akka.actor.ActorNotFound: Actor not found for: ActorSelection[Anchor(akka://flink/deadLetters), Path(/)] at akka.actor.ActorSelection$$anonfun$resolveOne$1.apply(ActorSelection.scala:65) at akka.actor.ActorSelection$$anonfun$resolveOne$1.apply(ActorSelection.scala:63) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.processBatch$1(BatchingExecutor.scala:67) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply$mcV$sp(BatchingExecutor.scala:82) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply(BatchingExecutor.scala:59) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply(BatchingExecutor.scala:59) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:72) at akka.dispatch.BatchingExecutor$Batch.run(BatchingExecutor.scala:58) at akka.dispatch.ExecutionContexts$sameThreadExecutionContext$.unbatchedExecute(Future.scala:74
Re: Running example in IntelliJ
Thanks Robert. On Mar 6, 2015, at 1:41 PM, Robert Metzger rmetz...@apache.org wrote: Hey, This little screencast shows how to run WordCount in IntelliJ. Note that it will take a bit more time the first time because IntelliJ will compile all required classes: https://www.youtube.com/watch?v=JIV_rX-OIQMfeature=youtu.be Let us know if you need more help. Robert On Fri, Mar 6, 2015 at 5:58 AM, Dulaj Viduranga vidura...@icloud.com wrote: Hello, Can someone help me with the steps on how to compile and run an example on IntelliJ
Re: Could not build up connection to JobManager
Hi Till, I’m sorry. It doesn’t seem to solve the problem. The taskmanager still tries a 10.0.0.0/8 IP. Best regards. On Mar 5, 2015, at 1:00 PM, Till Rohrmann till.rohrm...@gmail.com wrote: Hi Dulaj, I looked through your commit and noticed that the JobClient might not be listening on the right network interface. Your commit seems to fix it. I just want to understand the problem properly and therefore I opened a branch with a small change. Could you try out whether this change would also fix your problem? You can find the code here [1]. Would be awesome if you checked it out and let it run on your cluster setting. Thanks a lot Dulaj! [1] https://github.com/tillrohrmann/flink/tree/fixLocalFlinkMiniClusterJobClient On Thu, Mar 5, 2015 at 4:21 AM, Dulaj Viduranga vidura...@icloud.com wrote: The every change in the commit b7da22a is not required but I thought they are appropriate. On Mar 5, 2015, at 8:11 AM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, I found many other places “localhost” is hard coded. I changed them in a better way I think. I made a pull request. Please review. b7da22a https://github.com/viduranga/flink/commit/b7da22a562d3da5a9be2657308c0f82e4e2f80cd On Mar 4, 2015, at 8:17 PM, Stephan Ewen se...@apache.org wrote: If I recall correctly, we only hardcode localhost in the local mini cluster - do you think it is problematic there as well? Have you found any other places? On Mon, Mar 2, 2015 at 10:26 AM, Dulaj Viduranga vidura...@icloud.com wrote: In some places of the code, localhost is hard coded. When it is resolved by the DNS, it is posible to be directed to a different IP other than 127.0.0.1 (like private range 10.0.0.0/8). I changed those places to 127.0.0.1 and it works like a charm. But hard coding 127.0.0.1 is not a good option because when the jobmanager ip is changed, this becomes an issue again. I'm thinking of setting jobmanager ip from the config.yaml to these places. If you have a better idea on doing this with your experience, please let me know. Best.
Re: Could not build up connection to JobManager
Hi, The error message is, 21:06:01,521 WARN org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager. at org.apache.flink.client.program.Client.run(Client.java:327) at org.apache.flink.client.program.Client.run(Client.java:306) at org.apache.flink.client.program.Client.run(Client.java:300) at org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:55) at org.apache.flink.examples.java.wordcount.WordCount.main(WordCount.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:437) at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:353) at org.apache.flink.client.program.Client.run(Client.java:250) at org.apache.flink.client.CliFrontend.executeProgram(CliFrontend.java:371) at org.apache.flink.client.CliFrontend.run(CliFrontend.java:344) at org.apache.flink.client.CliFrontend.parseParameters(CliFrontend.java:1087) at org.apache.flink.client.CliFrontend.main(CliFrontend.java:1114) Caused by: java.io.IOException: JobManager at akka.tcp://flink@fe80:0:0:0:742b:7f78:fab5:68e2%11:6123/user/jobmanager not reachable. Please make sure that the JobManager is running and its port is reachable. at org.apache.flink.runtime.jobmanager.JobManager$.getJobManagerRemoteReference(JobManager.scala:957) at org.apache.flink.runtime.client.JobClient$.createJobClient(JobClient.scala:151) at org.apache.flink.runtime.client.JobClient$.createJobClientFromConfig(JobClient.scala:142) at org.apache.flink.runtime.client.JobClient$.startActorSystemAndActor(JobClient.scala:125) at org.apache.flink.runtime.client.JobClient.startActorSystemAndActor(JobClient.scala) at org.apache.flink.client.program.Client.run(Client.java:322) ... 15 more Caused by: akka.actor.ActorNotFound: Actor not found for: ActorSelection[Anchor(akka://flink/deadLetters), Path(/)] at akka.actor.ActorSelection$$anonfun$resolveOne$1.apply(ActorSelection.scala:65) at akka.actor.ActorSelection$$anonfun$resolveOne$1.apply(ActorSelection.scala:63) at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.processBatch$1(BatchingExecutor.scala:67) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply$mcV$sp(BatchingExecutor.scala:82) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply(BatchingExecutor.scala:59) at akka.dispatch.BatchingExecutor$Batch$$anonfun$run$1.apply(BatchingExecutor.scala:59) at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:72) at akka.dispatch.BatchingExecutor$Batch.run(BatchingExecutor.scala:58) at akka.dispatch.ExecutionContexts$sameThreadExecutionContext$.unbatchedExecute(Future.scala:74) at akka.dispatch.BatchingExecutor$class.execute(BatchingExecutor.scala:110) at akka.dispatch.ExecutionContexts$sameThreadExecutionContext$.execute(Future.scala:73) at scala.concurrent.impl.CallbackRunnable.executeWithValue(Promise.scala:40) at scala.concurrent.impl.Promise$DefaultPromise.scala$concurrent$impl$Promise$DefaultPromise$$dispatchOrAddCallback(Promise.scala:280) at scala.concurrent.impl.Promise$DefaultPromise.onComplete(Promise.scala:270) at akka.actor.ActorSelection.resolveOne(ActorSelection.scala:63) at org.apache.flink.runtime.akka.AkkaUtils$.getReference(AkkaUtils.scala:321) at org.apache.flink.runtime.jobmanager.JobManager$.getJobManagerRemoteReference(JobManager.scala:952) ... 20 more The exception above occurred while trying to run your command. Client log doesn’t seem to show any info, 21:06:01,521 WARN org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 21:06:01,935 INFO org.apache.flink.api.java.ExecutionEnvironment - The job has 0 registered types and 0 default Kryo serializers 21:06:02,857 INFO akka.event.slf4j.Slf4jLogger - Slf4jLogger started 21:06:02,909 INFO Remoting - Starting remoting 21:06:03,158 INFO Remoting
Re: Could not build up connection to JobManager
Glad I could help any way. :) When the address is set to “localhost” I cannot submit a job. It immediately fails. But the address is “127.0.0.1”, it is stuck a little whyle on DEPLOYING and the fails. Correct me if I’m wrong but I think since using the address, hardcoded in config file, won’t harm anything, it will be safer to use it rather than defining it in the code. On Mar 5, 2015, at 6:57 PM, Till Rohrmann trohrm...@apache.org wrote: Could you submit a job when you set the job manager address to localhost? I did not see any logging statements of received jobs. If you did, could you also send the logs of the client? The 0.0.0.0 to which the BlobServer binds works for me on my machine. I cannot remember that we had problems with that before. But I agree, we should set it to the network interface which the JobManager uses. I cannot explain why your fix solves the problem. It does not touch any of the JobClient/JobManager logic. I updated my local branch [1] with a fix for the BlobServer. Could you try it out again and send us the logs? Thanks a lot for your help Dulaj. On Thu, Mar 5, 2015 at 1:24 PM, Dulaj Viduranga vidura...@icloud.com wrote: But can you explain why did my fix solved it? On Mar 5, 2015, at 5:50 PM, Stephan Ewen se...@apache.org wrote: Hi Dulaj! Okay, the logs give us some insight. Both setups seem to look good in terms of TaskManager and JobManager startup. In one of the logs (127.0.0.1) you submit a job. The job fails because the TaskManager cannot grab the JAR file from the JobManager. I think the problem is that the BLOB server binds to 0.0.0.0 - it should bind to the same address as the JobManager actor system. That should definitely be changed... On Thu, Mar 5, 2015 at 10:08 AM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, This is the log with setting “localhost” flink-Vidura-jobmanager-localhost.log https://gist.github.com/viduranga/e9d43521587697de3eb5#file-flink-vidura-jobmanager-localhost-log And this is the log with setting “127.0.0.1” flink-Vidura-jobmanager-localhost.log https://gist.github.com/viduranga/5af6b05f204e1f4b344f#file-flink-vidura-jobmanager-localhost-log On Mar 5, 2015, at 2:23 PM, Till Rohrmann trohrm...@apache.org wrote: What does the jobmanager log says? I think Stephan added some more logging output which helps us to debug this problem. On Thu, Mar 5, 2015 at 9:36 AM, Dulaj Viduranga vidura...@icloud.com wrote: Using start-locat.sh. I’m using the original config yaml. I also tried changing jobmanager address in config to “127.0.0.1 but no luck. With my changes it works ok. The conf file follows. # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreements. See the NOTICE file # distributed with this work for additional information # regarding copyright ownership. The ASF licenses this file # to you under the Apache License, Version 2.0 (the # License); you may not use this file except in compliance # with the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an AS IS BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. #== # Common #== jobmanager.rpc.address: 127.0.0.1 jobmanager.rpc.port: 6123 jobmanager.heap.mb: 256 taskmanager.heap.mb: 512 taskmanager.numberOfTaskSlots: 1 parallelization.degree.default: 1 #== # Web Frontend #== # The port under which the web-based runtime monitor listens. # A value of -1 deactivates the web server. jobmanager.web.port: 8081 # The port uder which the standalone web client # (for job upload and submit) listens. webclient.port: 8080 #== # Advanced #== # The number of buffers for the network stack. # # taskmanager.network.numberOfBuffers: 2048 # Directories for temporary files. # # Add a delimited list for multiple directories, using the system directory # delimiter (colon ':' on unix) or a comma, e.g.: # /data1/tmp:/data2/tmp:/data3
Running example in IntelliJ
Hello, Can someone help me with the steps on how to compile and run an example on IntelliJ
Re: Could not build up connection to JobManager
Hi, I found many other places “localhost” is hard coded. I changed them in a better way I think. I made a pull request. Please review. b7da22a https://github.com/viduranga/flink/commit/b7da22a562d3da5a9be2657308c0f82e4e2f80cd On Mar 4, 2015, at 8:17 PM, Stephan Ewen se...@apache.org wrote: If I recall correctly, we only hardcode localhost in the local mini cluster - do you think it is problematic there as well? Have you found any other places? On Mon, Mar 2, 2015 at 10:26 AM, Dulaj Viduranga vidura...@icloud.com wrote: In some places of the code, localhost is hard coded. When it is resolved by the DNS, it is posible to be directed to a different IP other than 127.0.0.1 (like private range 10.0.0.0/8). I changed those places to 127.0.0.1 and it works like a charm. But hard coding 127.0.0.1 is not a good option because when the jobmanager ip is changed, this becomes an issue again. I'm thinking of setting jobmanager ip from the config.yaml to these places. If you have a better idea on doing this with your experience, please let me know. Best.
Not Flink related: IntelliJ cannot open maven projects
Hello, Not Flink related. IntelliJ cannot open maven projects. It is stuck on “Looking for available profiles….”. I can open the project in eclipse without any problem. Any ideas? No rush. Thanks.
Re: Could not build up connection to JobManager
The every change in the commit b7da22a is not required but I thought they are appropriate. On Mar 5, 2015, at 8:11 AM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, I found many other places “localhost” is hard coded. I changed them in a better way I think. I made a pull request. Please review. b7da22a https://github.com/viduranga/flink/commit/b7da22a562d3da5a9be2657308c0f82e4e2f80cd On Mar 4, 2015, at 8:17 PM, Stephan Ewen se...@apache.org wrote: If I recall correctly, we only hardcode localhost in the local mini cluster - do you think it is problematic there as well? Have you found any other places? On Mon, Mar 2, 2015 at 10:26 AM, Dulaj Viduranga vidura...@icloud.com wrote: In some places of the code, localhost is hard coded. When it is resolved by the DNS, it is posible to be directed to a different IP other than 127.0.0.1 (like private range 10.0.0.0/8). I changed those places to 127.0.0.1 and it works like a charm. But hard coding 127.0.0.1 is not a good option because when the jobmanager ip is changed, this becomes an issue again. I'm thinking of setting jobmanager ip from the config.yaml to these places. If you have a better idea on doing this with your experience, please let me know. Best.
Re: About FLINK-1537 Machine learning with Apache Flink
Hi, I would really like to know what are your high priority GSoC projects and that is it possible for me to have one to contribute this summer. I’ve played around and went through the flink system sources and I’m really interested in contributing to this project. I was interested in working on [FLINK-1537] Machine learning with Apache Flink project for GSoC, becase I have a past neural networks knowledge. But I see it is a Minor priority one. I'm wondering if you could help me to select a good high priority project. Thank you. On Feb 20, 2015, at 10:33 PM, Till Rohrmann trohrm...@apache.org wrote: Good to hear. Cheers, Till On Fri, Feb 20, 2015 at 5:31 PM, Dulaj Viduranga vidura...@icloud.com mailto:vidura...@icloud.com wrote: Great. I have already started to go through documentation. I’ll follow your directions and contact you when I’m up and ready. :) Best regards. Dulaj On Feb 19, 2015, at 10:49 PM, Till Rohrmann trohrm...@apache.org mailto:trohrm...@apache.org wrote: Hi Dulaj, first of all, sorry for my late reply. Yes, we're definitely making the Machine learning with Apache Flink a GSoC project and it's great to hear that you are interested in this topic. At the moment, I'm about to set Flink's machine learning library up with some basic algorithms. There is still some work to do in order to figure out in which direction it should finally head. But we are confident that we can provide a highly usable and still performant tool for many data scientists. Implementing algorithms with Apache Flink is a little bit different from regular programming, because the programming model is a little bit more restrictive. Therefore, I'd recommend to familiarize yourself a little bit with the system by by reading the documentation [1], going through the example jobs contained in the repo [2] and maybe even try to implement one job yourself. That is the best way to understand Flink. The next step would be try to tackle down one of the starter issues in order to get to know how the community works and to become visible for the community. You can find the starter issues here [3]. Afterwards we can brainstorm a little bit what you could do in the context of the GSoC project so that we can make a proposal. It would be great, but not strictly required, to have some knowledge of Scala, because some of the machine learning library will probably be implemented in Scala. Cheers, Till [1] http://flink.apache.org/docs/0.8/index.html http://flink.apache.org/docs/0.8/index.html [2] https://github.com/apache/flink/tree/master/flink-examples https://github.com/apache/flink/tree/master/flink-examples [3] https://issues.apache.org/jira/browse/FLINK-1582?jql=project%20%3D%20FLINK%20AND%20labels%20%3D%20Starter https://issues.apache.org/jira/browse/FLINK-1582?jql=project%20%3D%20FLINK%20AND%20labels%20%3D%20Starter On Tue, Feb 17, 2015 at 5:00 PM, Dulaj Viduranga vidura...@icloud.com mailto:vidura...@icloud.com wrote: Hi, I'm Dulaj Viduranga and I’m a 3rd year Computer Science and Engineering student at University of Moratuwa, Sri Lanka. I’m really interested about Machine learning with Apache Flink” Project and wondering if you are planing to make this a GSoC project. I have a 5 years Java experience and great knowledge and interest about machine learning. I haven’t used Flink or it’s machine learning library but I have a good experience with pylearn2 python neural network library and also I have made a neural network with java se from the scratch in my 2nd year. If you think I’m up for it, please let me know. Thank you. Dulaj Viduranga.
Access flink-conf.yaml data
Hi, Can someone help me on how to access the flink-conf.yaml configuration values inside the flink sources? Are these readily available as a map somewhere? Thanks.
[jira] [Created] (FLINK-1634) Fix Could not build up connection to JobManager issue on some systems
Dulaj Viduranga created FLINK-1634: -- Summary: Fix Could not build up connection to JobManager issue on some systems Key: FLINK-1634 URL: https://issues.apache.org/jira/browse/FLINK-1634 Project: Flink Issue Type: Bug Affects Versions: 0.9 Reporter: Dulaj Viduranga Priority: Critical Fix For: 0.9 In some systems, flink 0.9-SNAPSHOT gives an error (org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager.) when the taskmanager tries to connect to the jobmanager. This is because the taskmanager cannot resolve the IP where the jobmanager runs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLINK-1634) Fix Could not build up connection to JobManager issue on some systems
Dulaj Viduranga created FLINK-1634: -- Summary: Fix Could not build up connection to JobManager issue on some systems Key: FLINK-1634 URL: https://issues.apache.org/jira/browse/FLINK-1634 Project: Flink Issue Type: Bug Affects Versions: 0.9 Reporter: Dulaj Viduranga Priority: Critical Fix For: 0.9 In some systems, flink 0.9-SNAPSHOT gives an error (org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager.) when the taskmanager tries to connect to the jobmanager. This is because the taskmanager cannot resolve the IP where the jobmanager runs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Could not build up connection to JobManager
Hi, I found the fix for this issue and I'll create a pull request in the following day.
Re: Could not build up connection to JobManager
In some places of the code, localhost is hard coded. When it is resolved by the DNS, it is posible to be directed to a different IP other than 127.0.0.1 (like private range 10.0.0.0/8). I changed those places to 127.0.0.1 and it works like a charm. But hard coding 127.0.0.1 is not a good option because when the jobmanager ip is changed, this becomes an issue again. I'm thinking of setting jobmanager ip from the config.yaml to these places. If you have a better idea on doing this with your experience, please let me know. Best.
Re: Could not build up connection to JobManager
Here is the taskmanager log when I tried taskmanager.sh start flink-Vidura-taskmanager-localhost.log https://gist.github.com/anonymous/aef5a0bf8722feee9b97#file-flink-vidura-taskmanager-localhost-log On Feb 27, 2015, at 4:12 PM, Till Rohrmann trohrm...@apache.org wrote: It depends on how you started Flink. If you started a local cluster, then the TaskManager log is contained in the JobManager log we just don't see the respective log output in the snippet you posted. If you started a TaskManager independently, either by taskmanager.sh or by start-cluster.sh, then a file with the name format flink-user-taskmanager-hostname.log should be created in flink/log/. If the Flink directory is not shared by your cluster nodes, then you have to look on the machine on which you started the TaskManager. But since the JobManager binds to 127.0.0.1 I guess that you started a local cluster. Try whether you find some logging statements from the logger org.apache.flink.runtime.taskmanager.TaskManager in your log. Maybe you can upload the corresponding log file to [1] and post a link here. Greets, Till [1] https://gist.github.com/ On Thu, Feb 26, 2015 at 6:45 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, Can you tell me where I can find TaskManager logs. I can’t find them in logs folder? I don’t suppose I should run taskmanager.sh as well. Right? I’m using a OS X Yosemite. I’ll send you my ifconfig. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 options=3RXCSUM,TXCSUM inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1PERFORMNUD gif0: flags=8010POINTOPOINT,MULTICAST mtu 1280 stf0: flags=0 mtu 1280 en0: flags=8823UP,BROADCAST,SMART,SIMPLEX,MULTICAST mtu 1500 ether 60:03:08:a1:e0:f4 nd6 options=1PERFORMNUD media: autoselect (unknown type) status: inactive en1: flags=8963UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=60TSO4,TSO6 ether 72:00:02:32:14:d0 media: autoselect full-duplex status: inactive en2: flags=8963UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=60TSO4,TSO6 ether 72:00:02:32:14:d1 media: autoselect full-duplex status: inactive bridge0: flags=8822BROADCAST,SMART,SIMPLEX,MULTICAST mtu 1500 options=63RXCSUM,TXCSUM,TSO4,TSO6 ether 62:03:08:1a:fa:00 Configuration: id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0 maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200 root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0 ipfilter disabled flags 0x2 member: en1 flags=3LEARNING,DISCOVER ifmaxaddr 0 port 5 priority 0 path cost 0 member: en2 flags=3LEARNING,DISCOVER ifmaxaddr 0 port 6 priority 0 path cost 0 media: unknown type status: inactive p2p0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 2304 ether 02:03:08:a1:e0:f4 media: autoselect status: inactive awdl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1452 ether 06:56:3d:f6:60:08 nd6 options=1PERFORMNUD media: autoselect status: inactive ppp0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500 inet 10.218.98.228 -- 10.64.64.64 netmask 0xff00 utun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1380 inet6 fe80::b0d4:d4be:7e62:e730%utun0 prefixlen 64 scopeid 0xb inet6 fdd0:b291:7da7:9153:b0d4:d4be:7e62:e730 prefixlen 64 nd6 options=1PERFORMNUD On Feb 26, 2015, at 10:48 PM, Stephan Ewen se...@apache.org wrote: Hi Dulaj! Thanks for helping to debug. My guess is that you are seeing now the same thing between JobManager and TaskManager as you saw before between JobManager and JobClient. I have a patch pending that should help the issue (see https://issues.apache.org/jira/browse/FLINK-1608), let's see if that solves it. What seems not right is that the JobManager initially accepted the TaskManager and later the communication. Can you paste the TaskManager log as well? Also: There must be something fairly unique about your network configuration, as it works on all other setups that we use (locally, cloud, test servers, YARN, ...). Can you paste your ipconfig / ifconfig by any chance? Greetings, Stephan On Thu, Feb 26, 2015 at 4:33 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, It’s great to help out. :) Setting 127.0.0.1 instead of “localhost” in jobmanager.rpc.address, helped to build the connection to the jobmanager. Apparently localhost resolving is different in webclient and the jobmanager. I think it’s good to set jobmanager.rpc.address: 127.0.0.1 in future builds. But then I get this error when I tried to run examples. I don’t know if I
Re: Could not build up connection to JobManager
) at scala.runtime.AbstractPartialFunction$mcVL$sp.apply(AbstractPartialFunction.scala:25) 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:88) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) at akka.actor.ActorCell.invoke(ActorCell.scala:487) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:254) at akka.dispatch.Mailbox.run(Mailbox.scala:221) at akka.dispatch.Mailbox.exec(Mailbox.scala:231) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) Caused by: akka.pattern.AskTimeoutException: Ask timed out on [Actor[akka://flink/user/taskmanager#-1628133761]] after [10 ms] at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:333) at akka.actor.Scheduler$$anon$7.run(Scheduler.scala:117) at scala.concurrent.Future$InternalCallbackExecutor$.scala$concurrent$Future$InternalCallbackExecutor$$unbatchedExecute(Future.scala:694) at scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:691) at akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(Scheduler.scala:467) at akka.actor.LightArrayRevolverScheduler$$anon$8.executeBucket$1(Scheduler.scala:419) at akka.actor.LightArrayRevolverScheduler$$anon$8.nextTick(Scheduler.scala:423) at akka.actor.LightArrayRevolverScheduler$$anon$8.run(Scheduler.scala:375) at java.lang.Thread.run(Thread.java:745) The exception above occurred while trying to run your command. On Feb 26, 2015, at 12:46 AM, Stephan Ewen se...@apache.org wrote: Addition: To check whether a port is reachable, I think the easiest thing is to try and connect with a telnet client and see if the connection is refused. On Wed, Feb 25, 2015 at 8:15 PM, Stephan Ewen se...@apache.org wrote: Okay, the problem seems to be that even though both the client and the jobmanager use localhost as the host name, they resolve this to different IP addresses: In one case 127.0.0.1 in the other case 10.216.177.146 Also, the 127.0.0.1 address cannot communicate to 10.216.177.146 apparently. Can you help us debug this by checking the following: - Can you try and set jobmanager.rpc.address to 127.0.0.1 and see if that solves it? - Can you try and set jobmanager.rpc.address to the other address (10.216.177.146 or so) and see if that solves it? - Can you do start-cluster.sh, rather than start-local.sh and see whether the webfrontend displays that the TaskManager connects? - As a hard core test: Can you bring up the jobmanager, check where it connects (10.216.192.98:6123 or so) and see whether the port is reachable? We have recently updated how the Akka URLs are build, to work around a limitation in Akka. Seems that did not yet fully solve the issue. Thanks for helping us debug this, it is not the easiest immigration experience, but the outcome is probably extremely valuable for the project :-) Greetings, Stephan On Wed, Feb 25, 2015 at 4:03 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, Sorry for the delay to reply on this issue. the jobmanager.rpc.address is set to “localhost” already in conf.yaml. This can’t be an issue because the job manager web interface works fine which also runs on localhost bin/flink run jar doesn’t seem to work either. Let me send you my command and the result in terminal. bin/flink run /Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/examples/flink-java-examples-0.9-SNAPSHOT-WordCount.jar /Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/hamlet.txt $FLINK_DIRECTORY/count 20:32:16,442 WARN org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager. at org.apache.flink.client.program.Client.run(Client.java:327) at org.apache.flink.client.program.Client.run(Client.java:306) at org.apache.flink.client.program.Client.run(Client.java:300
Re: Could not build up connection to JobManager
Hi, Sorry for the delay to reply on this issue. the jobmanager.rpc.address is set to “localhost” already in conf.yaml. This can’t be an issue because the job manager web interface works fine which also runs on localhost bin/flink run jar doesn’t seem to work either. Let me send you my command and the result in terminal. bin/flink run /Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/examples/flink-java-examples-0.9-SNAPSHOT-WordCount.jar /Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/hamlet.txt $FLINK_DIRECTORY/count 20:32:16,442 WARN org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable org.apache.flink.client.program.ProgramInvocationException: Could not build up connection to JobManager. at org.apache.flink.client.program.Client.run(Client.java:327) at org.apache.flink.client.program.Client.run(Client.java:306) at org.apache.flink.client.program.Client.run(Client.java:300) at org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:55) at org.apache.flink.examples.java.wordcount.WordCount.main(WordCount.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:437) at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:353) at org.apache.flink.client.program.Client.run(Client.java:250) at org.apache.flink.client.CliFrontend.executeProgram(CliFrontend.java:371) at org.apache.flink.client.CliFrontend.run(CliFrontend.java:344) at org.apache.flink.client.CliFrontend.parseParameters(CliFrontend.java:1087) at org.apache.flink.client.CliFrontend.main(CliFrontend.java:1114) Caused by: java.io.IOException: JobManager at akka.tcp://flink@10.216.177.146:6123/user/jobmanager not reachable. Please make sure that the JobManager is running and its port is reachable. at org.apache.flink.runtime.jobmanager.JobManager$.getJobManagerRemoteReference(JobManager.scala:897) at org.apache.flink.runtime.client.JobClient$.createJobClient(JobClient.scala:151) at org.apache.flink.runtime.client.JobClient$.createJobClientFromConfig(JobClient.scala:142) at org.apache.flink.runtime.client.JobClient$.startActorSystemAndActor(JobClient.scala:125) at org.apache.flink.runtime.client.JobClient.startActorSystemAndActor(JobClient.scala) at org.apache.flink.client.program.Client.run(Client.java:322) ... 15 more Caused by: java.util.concurrent.TimeoutException: Futures timed out after [1 milliseconds] at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219) at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107) at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) at scala.concurrent.Await$.result(package.scala:107) at org.apache.flink.runtime.jobmanager.JobManager$.getJobManagerRemoteReference(JobManager.scala:893) ... 20 more The exception above occurred while trying to run your command. On Feb 25, 2015, at 1:29 AM, Stephan Ewen se...@apache.org wrote: BTW: Does still work if you enter localhost for jobmanager.rpc.address in your flink-conf.yaml ? On Tue, Feb 24, 2015 at 7:50 PM, Stephan Ewen se...@apache.org wrote: Hi! I think that this is a problem in the current master (probably in there since a few days ago). I am fixing it... Thanks for reporting it! Stephan On Tue, Feb 24, 2015 at 6:52 PM, Stephan Ewen se...@apache.org wrote: Hi Dulaj! The log suggests that the JobManager binds itself to the IP address 10.216.192.98 and the WebClient runs at 127.0.0.1 The 127.0.0.1 actor system cannot connect to the 10.216.192.98. Let me verify whether this is a quirk of your particular setup, or a bug recently introduces in the 0.9-SNAPSHOT. Does the command line work for you? (bin/flink run jar) taskmanager.numberOfTaskSlots: -1 is also okay, this will mean that the default of '1' is used. Greetings, Stephan On Tue, Feb 24, 2015 at 5:18 PM, Dulaj Viduranga vidura...@icloud.com wrote: Is taskmanager.numberOfTaskSlots: -1 normal? On Feb 24, 2015, at 9:44 PM, Robert Metzger rmetz...@apache.org wrote: Hi, I could not find the logfiles attached to your mails. I think
Re: Could not build up connection to JobManager
Is taskmanager.numberOfTaskSlots: -1 normal? On Feb 24, 2015, at 9:44 PM, Robert Metzger rmetz...@apache.org wrote: Hi, I could not find the logfiles attached to your mails. I think the mailinglists are not accepting attachments. Can you put the logs on gist.github.com? The configuration values are documented here: http://flink.apache.org/docs/0.8/config.html For the webclient's port its called webclient.port On Tue, Feb 24, 2015 at 5:04 PM, Dulaj Viduranga vidura...@icloud.com wrote: I tried to kill the job manager manually in the terminal and start it again but no luck. Also could you tell me if it’s possible to change webclient’s port (8080) ? On Feb 24, 2015, at 1:41 PM, Stephan Ewen se...@apache.org wrote: Hey Dulaj! As a contributor, I would go against the latest version, which is 0.9-SNAPSHOT. It may be in your case that the JobManager actor is down, but the process still lingers. (BTW: I have a patch pending that makes sure the process disappears when the actor via down). Could you have a look at the log flink-user-jobmanager-host-.log and see if there are any errors logged? Greetings, Stephan Am 24.02.2015 06:29 schrieb Dulaj Viduranga vidura...@icloud.com: The JobManager seems to run fine. I don't know. When I tried to run start-local.sh again, It shows the PID of the running JobManager and also :8081 runs fine. I want to contribute to the project and I could get a little boost if I could see the capabilities of FLINK. :) Will it be OK to use 0.8.1 as a developer? On Feb 24, 2015, at 04:15 AM, Stephan Ewen se...@apache.org wrote: Hi Dulaj, That error message indicates that the JobManager is not running. Are you sure that the JobManager runs properly? Anything in the JobManager logs? BTW: The 0.9 branch is under heavy development / changes. That is why it may behave a bit different on different days right now. I would recommend to use the 0.8.1 release for a stable experience. Greetings, Stephan On Mon, Feb 23, 2015 at 7:39 PM, Robert Metzger rmetz...@apache.org wrote: Thank you for the quick reply. The log you've send is from the webclient. Can you also send the log of the JobManager? On Mon, Feb 23, 2015 at 7:28 PM, Dulaj Viduranga vidura...@icloud.com wrote: Yes. It seams it is not a problem with the arguments. I tried two days but different error occurs. It seams the web client can’t connect to the job manager although it is running Right now, I can’t even get the webclient to run. ./bin/start-webclient.sh executes fine but I cannot connect to localhost:8080 (even with telnet or curl) Here is the log for jobManager 23:22:31,933 INFO org.apache.flink.client.web.WebInterfaceServer - Setting up web frontend server, using web-root directory 'jar: file:/Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/lib/flink-clients-0.9-SNAPSHOT.jar!/web-docs '. 23:22:31,934 INFO org.apache.flink.client.web.WebInterfaceServer - Web frontend server will store temporary files in '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2cgn/T', uploaded jobs in '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2cgn/T/webclient-jobs', plan-json-dumps in '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2cgn/T/webclient-plans'. 23:22:31,934 INFO org.apache.flink.client.web.WebInterfaceServer - Web-frontend will submit jobs to nephele job-manager on localhost, port 6123. 23:22:32,580 INFO akka.event.slf4j.Slf4jLogger - Slf4jLogger started 23:22:32,625 INFO Remoting - Starting remoting 23:22:32,838 INFO Remoting - Remoting started; listening on addresses :[akka.tcp:// JobsInfoServletActorSystem@127.0.0.1:51517] 23:23:48,119 WARN Remoting - Tried to associate with unreachable remote address [akka.tcp:// flink@10.218.98.169:6123]. Address is now gated for 5000 ms, all messages to this address will be delivered to dead letters. Reason: Operation timed out: /10.218.98.169:6123 23:23:48,124 ERROR org.apache.flink.client.WebFrontend - Unexpected exception: Could not find job manager at specified address akka.flink@10.218.98.169:6123/user/jobmanager'tcp:// flink@10.218.98.169:6123/user/jobmanager. java.lang.RuntimeException: Could not find job manager at specified address akka.flink@10.218.98.169:6123/user/jobmanager'tcp:// flink@10.218.98.169:6123/user/jobmanager. at org.apache.flink.client.web.JobsInfoServlet.init(JobsInfoServlet.java:82) at org.apache.flink.client.web.WebInterfaceServer.init(WebInterfaceServer.java:158) at org.apache.flink.client.WebFrontend.main(WebFrontend.java:74) On Feb 23, 2015, at 11:46 PM, Robert Metzger rmetz...@apache.org wrote: Hi, you said in the other email thread that the error only occurs for Wordcount, not for Kmeans. Can you copy me the commands for both examples? I can
Could not build up connection to JobManager
I’m getting Could not build up connection to JobManager.” When i tried to run the wordCount example. Can anyone help? Dulaj
Re: Deprecated error building flink
Hi, But I’m using Oracle java 8 (javac 1.8.0_05). On Feb 22, 2015, at 6:32 PM, Robert Metzger rmetz...@apache.org wrote: Hi Dulaj, you are using an unsupported compiler to compile Flink. You can compile Flink only with OpenJDK 6 and all JDKs above 6. The Oracle JDK 6's compiler contains a bug. You can run Flink with all JREs 6+ (including Oracle JDK 6). I would recommend you to upgrade your Java version to 7 anyways, because 6 doesn't receive any security updates anymore. On Sun, Feb 22, 2015 at 12:55 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi all, I’m new here. I had some problems building flink on my mac. Could someone please take a look and help me out..? Dulaj Viduranga. [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.flink:flink-streaming-examples:jar:0.9-SNAPSHOT [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-jar-plugin @ org.apache.flink:flink-streaming-examples:[unknown-version], /Users/Vidura/Documents/Development/flink/flink-staging/flink-streaming/flink-streaming-examples/pom.xml, line 462, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] Reactor Build Order: [INFO] [INFO] flink [INFO] flink-shaded [INFO] flink-core [INFO] flink-java [INFO] flink-runtime [INFO] flink-compiler [INFO] flink-clients [INFO] flink-test-utils [INFO] flink-scala [INFO] flink-examples [INFO] flink-java-examples [INFO] flink-scala-examples [INFO] flink-staging [INFO] flink-streaming [INFO] flink-streaming-core [INFO] flink-tests [INFO] flink-avro [INFO] flink-jdbc [INFO] flink-spargel [INFO] flink-hadoop-compatibility [INFO] flink-streaming-scala [INFO] flink-streaming-connectors [INFO] flink-streaming-examples [INFO] flink-hbase [INFO] flink-gelly [INFO] flink-hcatalog [INFO] flink-tachyon [INFO] flink-quickstart [INFO] flink-quickstart-java [INFO] flink-quickstart-scala [INFO] flink-contrib [INFO] flink-yarn [INFO] flink-dist [INFO] flink-yarn-tests [INFO] [INFO] [INFO] Building flink 0.9-SNAPSHOT [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.pom (10 KB at 1.8 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.10/apache-rat-project-0.10.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.10/apache-rat-project-0.10.pom (18 KB at 13.9 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.jar (42 KB at 31.8 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.pom (8 KB at 8.0 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.jar (33 KB at 27.4 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ flink-parent --- [INFO] Deleting /Users/Vidura/Documents/Development/flink/target [INFO] [INFO] --- maven-checkstyle-plugin:2.12.1:check (validate) @ flink-parent --- [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven) @ flink-parent --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ flink-parent --- [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ flink-parent --- [INFO] [INFO] --- maven-shade-plugin:2.3:shade (default) @ flink-parent --- [INFO] Excluding org.apache.commons:commons-lang3:jar:3.3.2 from the shaded jar. [INFO] Excluding org.slf4j:slf4j-api:jar:1.7.7 from the shaded jar. [INFO] Excluding org.slf4j:slf4j-log4j12:jar:1.7.7 from the shaded jar. [INFO] Excluding log4j:log4j:jar:1.2.17 from the shaded jar. [INFO] Replacing original artifact with shaded artifact. [INFO] [INFO] --- maven
Re: Deprecated error building flink
Oh yes. :) It runs on 1.6. How could I fix that? On Feb 22, 2015, at 6:37 PM, Robert Metzger rmetz...@apache.org wrote: Can you run mvn -version to verify that? Maybe maven is using a different java version? On Sun, Feb 22, 2015 at 2:05 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi, But I’m using Oracle java 8 (javac 1.8.0_05). On Feb 22, 2015, at 6:32 PM, Robert Metzger rmetz...@apache.org wrote: Hi Dulaj, you are using an unsupported compiler to compile Flink. You can compile Flink only with OpenJDK 6 and all JDKs above 6. The Oracle JDK 6's compiler contains a bug. You can run Flink with all JREs 6+ (including Oracle JDK 6). I would recommend you to upgrade your Java version to 7 anyways, because 6 doesn't receive any security updates anymore. On Sun, Feb 22, 2015 at 12:55 PM, Dulaj Viduranga vidura...@icloud.com wrote: Hi all, I’m new here. I had some problems building flink on my mac. Could someone please take a look and help me out..? Dulaj Viduranga. [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.flink:flink-streaming-examples:jar:0.9-SNAPSHOT [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-jar-plugin @ org.apache.flink:flink-streaming-examples:[unknown-version], /Users/Vidura/Documents/Development/flink/flink-staging/flink-streaming/flink-streaming-examples/pom.xml, line 462, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] Reactor Build Order: [INFO] [INFO] flink [INFO] flink-shaded [INFO] flink-core [INFO] flink-java [INFO] flink-runtime [INFO] flink-compiler [INFO] flink-clients [INFO] flink-test-utils [INFO] flink-scala [INFO] flink-examples [INFO] flink-java-examples [INFO] flink-scala-examples [INFO] flink-staging [INFO] flink-streaming [INFO] flink-streaming-core [INFO] flink-tests [INFO] flink-avro [INFO] flink-jdbc [INFO] flink-spargel [INFO] flink-hadoop-compatibility [INFO] flink-streaming-scala [INFO] flink-streaming-connectors [INFO] flink-streaming-examples [INFO] flink-hbase [INFO] flink-gelly [INFO] flink-hcatalog [INFO] flink-tachyon [INFO] flink-quickstart [INFO] flink-quickstart-java [INFO] flink-quickstart-scala [INFO] flink-contrib [INFO] flink-yarn [INFO] flink-dist [INFO] flink-yarn-tests [INFO] [INFO] [INFO] Building flink 0.9-SNAPSHOT [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.pom (10 KB at 1.8 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.10/apache-rat-project-0.10.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.10/apache-rat-project-0.10.pom (18 KB at 13.9 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.10/apache-rat-plugin-0.10.jar (42 KB at 31.8 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.pom (8 KB at 8.0 KB/sec) Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1.jar (33 KB at 27.4 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ flink-parent --- [INFO] Deleting /Users/Vidura/Documents/Development/flink/target [INFO] [INFO] --- maven-checkstyle-plugin:2.12.1:check (validate) @ flink-parent --- [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven) @ flink-parent --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ flink-parent --- [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ flink-parent --- [INFO] [INFO] --- maven-shade-plugin:2.3:shade (default) @ flink-parent --- [INFO] Excluding org.apache.commons:commons-lang3
Move Nutch to Hadoop 2.X
Hi, My name is Dulaj Viduranga and I’m a 3rd year Computer Science and Engineering student at University of Moratuwa, Sri Lanka. I’m excited about Move Nutch to Hadoop 2.X project and I would like to participate in contributing to the project. Also If you are willing to, I’m very excited to have this, as my GSoC 2015 project this summer. Please let me know how to get involved. Thank you. Dulaj Viduranga.
[sympy] Re: GSoC Organization Application
Hi, I'm new to the project. I'm a 3rd year Computer Science and Engineering student and I have a 5 years experience in C++, C and Java. I'm very excited about csympy project and wondering if I could contribute to it as this year's GSoC project? On Tuesday, February 10, 2015 at 4:29:01 AM UTC+5:30, Aaron Meurer wrote: The GSoC organization application period has started. The application deadline is February 20. Action items: - If you are a prospective student, you don't need to do anything yet. Just continue to interact with the community here, on GitHub, and on Gitter. - If you are willing to mentor, please add your name to the bottom of https://github.com/sympy/sympy/wiki/GSoC-2015-Ideas. This is very important. Google won't accept our application if we don't have any potential mentors. It also affects how many slots we get. Even if you are only willing to mentor certain kinds of projects, still put your name there, with the projects you will mentor. - Everyone, please review the application https://github.com/sympy/sympy/wiki/GSoC-2015-Organization-Application. As of yet, this is still a copy of last year's application. I will go through later and at least make sure that the questions are still correct. Feel free to just make changes to the wiki page. I will review all changes that come in. If you have any suggestions that you would like to discuss regarding the application, feel free to do so here. Aaron Meurer -- You received this message because you are subscribed to the Google Groups sympy group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/477b7b39-8b0b-4f71-85df-7c7a496abb80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
