Hi, I’m contracting (via Algoteq I'm writing from here) for a Fortune 500
financial institution with a global footprint. I’m under NDA, so I can’t
name the company, but I’m happy to provide all the technical details I can.
We've run into an issue with Ignite there I'd need your advice on.

So, to cut a long story short - it seems that in very rare cases, Apache
Ignite's Continuous Query can miss an entry when the cache is hammered with
new records. Which is a real-life scenario for us. I have a demo project
that reproduces this, although it’s important to note that it took 8 hours
for a script continuously repeating the test case to trigger it.

I.e. yes it's a rare problem... but it happens sometimes indeed, and we
can't afford losing records there, it's financial stuff which just can't be
lost.

The problem demo is available here and includes ready-made logs:
https://github.com/new-mikha/ignite-missing-entry-demo

Hopefully the README explains all the details, but I’d be happy to clarify
anything if needed.

I’d appreciate any clues about this problem. Thanks!

Best regards,
Michael Karmazin

-- 


Visit our website at http://www.algoteq.com <http://www.algoteq.com>


Privileged/Confidential information may be contained in this message and 
may be subject to legal privilege. Access to this e-mail by anyone other 
than the intended is unauthorised. If you are not the intended recipient 
(or responsible for delivery of the message to such person), you may not 
use, copy, distribute or deliver to anyone this message (or any part of its 
contents) or take any action in reliance on it. In such case, you should 
destroy this message, and notify us immediately. If you have received this 
email in error, please notify us immediately by e-mail and delete the 
e-mail from your computer. If you or your employer does not consent to 
internet e-mail messages of this kind, please notify us immediately. All 
reasonable precautions have been taken to ensure no viruses are present in 
this e-mail. As Algoteq Pty Ltd cannot accept responsibility for any loss 
or damage arising from the use of this e-mail or attachments we recommend 
that you subject these to your virus checking procedures prior to use. The 
views, opinions, conclusions and other informations expressed in this 
electronic mail are not given or endorsed by the company unless otherwise 
indicated by an authorised representative independent of this message.

Reply via email to