Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
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 feat
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18308
LGTM. BTW can you please complement the PR description, thanks.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18308
Jenkins test this please
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #78086 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78086/testReport)**
for PR 18308 at commit
[`00a42e7`](https://github.com/apache/spark/commit/00
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #78086 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78086/testReport)**
for PR 18308 at commit
[`00a42e7`](https://github.com/apache/spark/commit/0
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78086/
Test FAILed.
---
Github user ihazem commented on the issue:
https://github.com/apache/spark/pull/18308
@jerryshao - I pushed another commit fixing removedExecutorId and removing
';'...thx for feedback on that.
Regarding the edge case where the block manager was already removed and
could pote
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18308
ok to test
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #78126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78126/testReport)**
for PR 18308 at commit
[`0f1c467`](https://github.com/apache/spark/commit/0f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #78126 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78126/testReport)**
for PR 18308 at commit
[`0f1c467`](https://github.com/apache/spark/commit/0
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78126/
Test FAILed.
---
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18308
> I wonder if whether executor is completely gone or whether executor is
still there but has no cached RDD, if both scenarios return false.
Yes, that's the case, we cannot differentiate t
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #3799 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3799/testReport)**
for PR 18308 at commit
[`0f1c467`](https://github.com/apache/spark/commit/0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18308
**[Test build #3799 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3799/testReport)**
for PR 18308 at commit
[`0f1c467`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18308
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 feat
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18308
Ping @ihazem
---
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 t
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18308
Ping @ihazem to update or close
---
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
Github user ihazem commented on the issue:
https://github.com/apache/spark/pull/18308
@srowen - I modified to take @vanzin recommendation of putting the logic in
the logInfo call instead. I'm open to hearing any recommendations on using a
less expensive call. Thx!
---
If your projec
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18308
Can you update the title to:
```
[SPARK-21099][Core] Log cachedExecutorIdleTimeoutS instead of
executorIdleTimeoutS if the executor has cached blocks
```
?
---
If your project
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18308
Is this the final modified code @ihazem , why do you check
`hasCachedBlocks` both inside and outside of logInfo statement? Also the code
is too long.
Can you please at least do a round of
Github user ihazem commented on the issue:
https://github.com/apache/spark/pull/18308
@jerryshao - sorry about that...let me remove the logic outside the logInfo
statements. Missed that. I'll do some more self-review and peer-review going
fwd before submitting to not waste everyone's
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18308
There is no cheaper call you can make. Which is the problem here. So either
you have to modify the code so that it keeps track of why the executor has
timed out (i.e. more state being passed around),
24 matches
Mail list logo
