Nikolay, First the error is printed on the map node, then on the reduce node, and then the exception is thrown from the method that triggered the execution. The compute grid seems to use the "print an error message and delegate exception to the caller" which doesn't make much sense. If you don't know what to do with an error and delegate it to the caller, what's the point in printing it to log? This is the kind of information that should only be printed when debug logging is enabled.
I created a ticket for this issue: https://issues.apache.org/jira/browse/IGNITE-13487 Denis пн, 10 авг. 2020 г. в 18:45, Nikolay Izhikov <nizhi...@apache.org>: > Hello, Vasiliy. > > This messages are shown on the different nodes, isn’t it? > > > 10 авг. 2020 г., в 18:34, Vasiliy Sisko <vsi...@gridgain.com> > написал(а): > > > > In case of errors in user computations the Ignite Compute Grid produces a > > lot of errors into the log. > > In the worst way it produces the next messages: > > 1. Failed to execute job: … > > 2. Failed to reduce job results: … > > 3. Failed to execute task: … > > > > There is a suggestion to decrease log level for first and second messages > > to DEBUG level, because of the third message will still be shown. > > > > -- > > Vasiliy Sisko > >
