Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-90513119
@marsishandsome is this change needed then or is that workaround actually
the right way to do this?
---
If your project is set up for it, you can reply to this email and
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-90516225
@srowen This change is not needed.
As Spark-5331 said, Spark provides many services both to internal and
external. Spark should provide a way for users
Github user marsishandsome closed the pull request at:
https://github.com/apache/spark/pull/5095
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-90307943
@yongjiaw Thanks for your advice. As a workaround I set the hostname to the
ip and it works. I like the solution of Spark-5113.
---
If your project is set up
Github user yongjiaw commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-89798959
You can probably just use the command: sudo hostname ip to let spark's
blocker manager pickup the ip you wanted from the OS hostname.
For more general solution,
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-86203897
@marsishandsome did you get it working on your network? Is this patch no
longer needed?
---
If your project is set up for it, you can reply to this email and have
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-86236076
@andrewor14 Yes, it works in my network.
Currently spark can only find the machine's hostname and use it to
communicate with others.
I thinks spark should
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-85508290
In our local network, the yarn-node do not know the hostname of the
client. So I have to set spark.driver.host to the client's ip address, so the
driver will use it's
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-85533219
@tgravescs Yes, DNS in our network is not properly configured.
The yarn-node cannot connect to the client by the hostname of the client
machine.
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-85030899
@marsishandsome This seems like a bit of an odd use case. If the
spark.driver.host is something different then actual host then errors are going
to occur. Why are
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-85257353
@tgravescs You are right. Maybe we should provide two choices: Ip and
Hostname. Both will be automatically figured out by Spark.
---
If your project is set up
Github user marsishandsome commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-85256831
@tgravescs In our local network, the yarn-node do not know the hostname of
the client. So I have to set spark.driver.host to the client's ip address, so
the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5095#issuecomment-83802093
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
13 matches
Mail list logo
