[IGNITE-8501] Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Assignee: Stanislav Lukyanov
• Reporter: Stanislav Lukyanov
• Created: 15/May/18 15:08
• Updated: 26/Jun/18 17:50
• Resolved: 22/May/18 13:48

Description

`GridServiceProxy::invokeMethod` attempts to invoke a method of an Ignite service and performs retries in case the invocation procedure throws `GridServiceNotFoundException` or `ClusterTopologyCheckedException` (these exceptions may be thrown in case the service assignments were already calculated, but the service instance was not yet created and initialized on the affinity server).
After the fix IGNITE-7904 the exception type thrown by the remote invocation code changed to `IgniteCheckedException` (with a cause being `GridServiceNotFoundException` or `ClusterTopologyCheckedException`). Because of that, the retry doesn't work now.
Need to fix the code to correctly handle new exception chain.

Issue Links

• is related to: IGNITE-7904 ComputeTaskFuture.get() throws incorrect exception if ComputeTask.result() throws IgniteException
• is related to: IGNITE-1478 Service cannot be used on remote node immediately after deployment.
• links to: GitHub Pull Request #4004