[GitHub] [spark] tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait

2020-03-25 Thread GitBox
tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait URL: https://github.com/apache/spark/pull/27943#issuecomment-603866859 I'll take a closer look this afternoon, but can you update the description to just

[GitHub] [spark] tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait

2020-03-23 Thread GitBox
tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait URL: https://github.com/apache/spark/pull/27943#issuecomment-602733405 ok thanks for the description. So are you only trying to fail faster when only fetching

[GitHub] [spark] tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait

2020-03-23 Thread GitBox
tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait URL: https://github.com/apache/spark/pull/27943#issuecomment-602605054 So I'm really not clear on what the desired behavior is and I think we are using

[GitHub] [spark] tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait

2020-03-19 Thread GitBox
tgravescs commented on issue #27943: [SPARK-31179] Fast fail the connection while last connection failed in the last retry IO wait URL: https://github.com/apache/spark/pull/27943#issuecomment-601202011 > Currently we just run and timeout 3 times, and this PR proposes to fail fast.