[
https://issues.apache.org/jira/browse/SPARK-19450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-19450.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 16790
[https://github.com/apache/spark/pull/16790]
> Replace askWithRetry with askSync.
> ----------------------------------
>
> Key: SPARK-19450
> URL: https://issues.apache.org/jira/browse/SPARK-19450
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.1.0
> Reporter: jin xing
> Assignee: jin xing
> Priority: Minor
> Fix For: 2.2.0
>
>
> *askSync* is already added in *RpcEndpointRef* (see SPARK-19347 and
> https://github.com/apache/spark/pull/16690#issuecomment-276850068) and
> *askWithRetry* is marked as deprecated.
> As mentioned
> SPARK-18113(https://github.com/apache/spark/pull/16503#event-927953218):
> ??askWithRetry is basically an unneeded API, and a leftover from the akka
> days that doesn't make sense anymore. It's prone to cause deadlocks (exactly
> because it's blocking), it imposes restrictions on the caller (e.g.
> idempotency) and other things that people generally don't pay that much
> attention to when using it.??
> Since *askWithRetry* is just used inside spark and not in user logic. It
> might make sense to replace all of them with *askSync*.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
