ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov ...@apache.org>
Subject Re: Add new event in putblic API
Date Mon, 07 Nov 2016 07:45:24 GMT
Dmitriy,

In cases where ContinuousQuery Event unmarshalling failed we have to inform
node's owner somehow.
Failed CQ event means you'll just get no event, no exception, and you'll
have no need to read logs.
Currently, we have no possibility to inform user except writing error
message to logs.

So, we have two ways to inform user: 1) to extend CQ API with new method
listentFailedEvents() 2) or to let user listen for UnhandledExceptionEvent
First case will break old sources using Ignite CQ in case method will be
required, and gives no profit in case it will be optional.
Second case will allow to listen such events or/and to see them at some
management tool (eg. Visor).

So, current solution is to log such failures, write them to
ExceptionRegistry and inform user using UnhandledExceptionEvent (via
listener or management console).

On Fri, Nov 4, 2016 at 6:34 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Dmitriy, I am not sure how a public even would help fixing internal error
> handling. Also, the ticket has too many comments which makes it difficult
> to understand. Any chance you could provide the final proposal here?
>
> On Thu, Nov 3, 2016 at 8:01 AM, Dmitriy Govorukhin <
> dmitriy.govorukhin@gmail.com> wrote:
>
> > HI all, I think what we need add new event for handling
> > unhandled exception. We have some exception which not handled, new
> > event (UnhandledExceptionEvent) can
> > help know if was unhandled exception. Let's discuss. More details about
> > reason IGNITE-2079 <https://issues.apache.org/jira/browse/IGNITE-2079>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message