Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13658
@subrotosanyal we should close this PR until we understand the actual cause
of the failure. Please provide more information in the JIRA (like full
application logs and maybe sample code to trigger
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13658
I understand you don't want to use a custom distro, but your patch is
masking what could be a real issue, and that's the worrying part. We should
understand really why the issue is happening in the
Github user subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13658
hi @vanzin
Even I am surprised to see that notify was not triggered somehow.
> Is your code perhaps setting "spark.master" to "local" or something that
is not "yarn-cluster"
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13658
@subrotosanyal ping
---
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,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13658
@subrotosanyal I'd close this out if we haven't been able to rule out the
points above.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13658
I agree with Saisai that the real question is why the context is not
registering with the AM.
Is your code perhaps setting "spark.master" to "local" or something that is
not "yarn-cluster"
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/13658
I'm just wondering the real cause of this issue, why it is not notified,
normally it should be worked. your fix might be one option, but I'd like to
find out the root cause.
---
If your project
Github user subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13658
hi @jerryshao
Isn't this fix going to deal with the problem?
---
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
Github user subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13658
so our client(JVM) spawns a SparkContext and uses the same to submit Spark
Jobs to the cluster i.e. the we are using Spark client mode.
---
If your project is set up for it, you can reply
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/13658
Thanks for the explanation, but I'm not sure why notify is not worked,
maybe we should find out the problem there. Also is your application a Spark
application submitted through yarn or just a
Github user subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13658
hi @jerryshao
`16/06/13 10:50:35 INFO yarn.ApplicationMaster: Final app status:
SUCCEEDED, exitCode: 0
16/06/13 10:50:35 DEBUG yarn.ApplicationMaster: Done running users class
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/13658
@subrotosanyal is there any problem in the previous code, can you please
elaborate it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13658
hi @vanzin ,
Could you please have a look into this pull request?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13658
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 project does not have this
14 matches
Mail list logo
