You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2023/03/16 20:19:00 UTC
[jira] [Updated] (IGNITE-19055) CPP: Incorrect Compute task failure handling
[ https://issues.apache.org/jira/browse/IGNITE-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Petrov updated IGNITE-19055:
------------------------------------
Component/s: platforms
> CPP: Incorrect Compute task failure handling
> --------------------------------------------
>
> Key: IGNITE-19055
> URL: https://issues.apache.org/jira/browse/IGNITE-19055
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Reporter: Mikhail Petrov
> Priority: Major
>
> All calculation methods, except for those whose names contain the word "affinity", fail to handle errors that occure during task execution.
> They just fail with the following message:
> {code:java}
> Broken promise. Value will never be set due to internal error.
> {code}
> It appears that the CPP IgniteEnvironment::ComputeTaskComplete method does not deserialize the exception information at all, which is generated by the Java side (see PlatformAbstractTask#onDone).
> DotNet does not have such problems due to the correct implementation of exception info deserialization (see Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.ComputeTaskComplete).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)