Dmitriy, Shouldn't we report serialization problem properly instead? We already had a problem when node hanged during job execution in case it was impossible to deserialize the job on receiver side. It was resolved properly - we caught exception on receiver side and reported it back sender side.
I believe we must do the same for services. Otherwise we may end up in messy API which doesn't resolve original problem. Vladimir. On Tue, Nov 15, 2016 at 4:38 PM, Dmitriy Karachentsev < [email protected]> wrote: > Hi Igniters! > > I'd like to modify our public API and add IgniteServices.serviceProxy() > method with timeout argument as part of the task > https://issues.apache.org/jira/browse/IGNITE-3862 > > In short, without timeout, in case of serialization error, or so, service > acquirement may hang and infinitely log errors. > > Do you have any concerns about this change? > > Thanks! > Dmitry. >
