gt; Hi Ilya,
>>
>> Sure, the complete code could be found here:
>> https://github.com/ifedorenkov-tda/ignite-experiments/tree/continuous-query-with-transformer-missing-events
>> Just start 3-4 server nodes and then 1 client node.
>>
>> Best regards,
>&g
https://issues.apache.org/jira/browse/IGNITE-14981
чт, 17 июн. 2021 г. в 14:51, Ilya Kasnacheev :
> Hello!
>
> This is unfortunate. Do we have a ticket for it?
>
> As a workaround, one may set query warning timeout to 1 ms and then see
> these detailed messages in the log.
>
> Regards,
> --
> Ily
on?
>>>
>>> Reference to SO question:
>>>
>>> https://stackoverflow.com/questions/61410519/apache-ignite-2-8-0-node-metrics-system-view-doesnt-exist/61461243
>>>
>>>
>>> Best regards,
>>> Ivan Fedorenkov
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>
DhtAtomicCache.update(GridDhtAtomicCache.java:2097)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1914)
... 28 more
Best regards,
Ivan Fedorenkov
Thank you, Alex!
There are no other warning or error messages in ignite log around that
time. Nodes were stable. Though I can provide a full log and the source
code of the entity, I can see that the "pendingEvts" field of the "
CacheContinuousQueryHandler" class is being used without a lock. Could
gging, especially for
> org.apache.ignite.internal.processors.cache.query.continuous
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 27 мая 2020 г. в 09:17, Ivan Fedorenkov :
>
>> Thank you, Alex!
>>
>> There are no other warning or error messages in ignite log around that
>> time. Nodes were stab
