It is really strange. It's right that the CliFrontend now resolves
localhost to the correct local address 10.218.100.122. Moreover, according
to the logs, the JobManager is also started and binds to akka.tcp://
flink@10.218.100.122:6123. According to the logs, this is also the address
the
Could you please upload the logs? They would be really helpful.
On Mon, Mar 16, 2015 at 6:11 PM, Dulaj Viduranga vidura...@icloud.com
wrote:
Hi,
I tested the update but it’s still the same. I think it isn’t a problem
with my system because, I have an XAMPP server working totally fine (I
There was an issue for this:
https://issues.apache.org/jira/browse/FLINK-1634
Can we close it then?
On Sat, Mar 14, 2015 at 9:16 PM, Dulaj Viduranga vidura...@icloud.com
wrote:
Hay Stephan,
Great to know you could fix the issue. Thank you on the update.
Best regards.
On Mar 14, 2015, at
Hey Dulaj!
One thing you can try is to add to the JVM startup options (in the scripts
in the bin folder) the option -Djava.net.preferIPv4Stack=true and see
if that helps it?
Stephan
On Sat, Mar 14, 2015 at 4:29 AM, Dulaj Viduranga vidura...@icloud.com
wrote:
Hi,
Still this is no luck. I’ll
Hey Dulaj!
Forget what I said in the previous email. The issue with the wrong address
binding seems to be solved now. There is another issue that the embedded
taskmanager does not start properly, for whatever reason. My gut feeling is
that there is something wrong
There is a patch pending that
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
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
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
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
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
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
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
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:
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
Hi,
I found the fix for this issue and I'll create a pull request in the following
day.
Calling:
java -cp ../examples/flink-java-examples-0.9-SNAPSHOT-KMeans.jar
org.apache.flink.examples.java.clustering.util.KMeansDataGenerator 500 10
0.08
Will not connect to Flink. Its just running a standalone KMeans data
generator, not KMeans.
I would suspect that the KMeans example is not
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
Wow, great. Can you tell us what the issue was?
Am 02.03.2015 09:31 schrieb Dulaj Viduranga vidura...@icloud.com:
Hi,
I found the fix for this issue and I'll create a pull request in the
following day.
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
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
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:
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
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
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
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
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
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
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
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
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 not really believe that there is a difference between the two jobs.
Can you also send us the contents of the jobmanager log file?
Best,
Robert
30 matches
Mail list logo
