Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/157#issuecomment-37762544
Hey @baishuo I'd separately try to debug why SPARK_JAVA_OPTS isn't working.
In general we probably don't want to hard code debugging options like this in
the launcher.
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/157#issuecomment-37761089
That is weird - you can see the use of SPARK_JAVA_OPTS just a few lines
above in the patch you submitted.
---
If your project is set up for it, you can reply to this emai
Github user baishuo commented on the pull request:
https://github.com/apache/spark/pull/157#issuecomment-37760047
Thank you for mridulmâs updateã I had set SPARK_JAVA_OPTS of one
worker to "-Xdebug
-Xrunjdwp:transport=dt_socket,address=18000,server=y,suspend=y" and try to do a
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/157#issuecomment-37758977
This can be done with SPARK_JAVA_OPTS set to java debug options.
That goes to master and executors.
Practically, particularly in multi-tennet deployments this n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/157#issuecomment-37758897
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 proj
GitHub user baishuo opened a pull request:
https://github.com/apache/spark/pull/157
Update CommandUtils.scala
enable the user can do remote-debugging on the ExcutorRunner Process. we
need one flag to enable this function: spark.excutor.debug, an other flag
spark.excutor.debug.port
