Veena,
Ignite shouldn't be waiting for the storage spi. It first starts all its
components and when an
Event is ready to be recorded, the storage SPI is invoked. This scenario
tests out ok.
Send a reproducer and I'll take a look.
Thanks, Alex
--
Sent from:
Thanks Alex,
Will try and see if I can create a reproducer.
>>If Ignite hasn't fully started, it will wait( U.awaitQuiet(startLatch); )
until it has, before returning the instance.
Does the Ignition.start wait for the storage spi to return from record, to
start ? since the storage spi is waiting
Veena,
I am not getting the same issue/thread dump when I run a similar use case.
In your case it looks like Ignite has not fully started before
Ignition.ignite() has been called.
The check inside that function is specifically designed to prevent such
cases.
Here is the function you are
Hi Alex,
1. How is the storage spi record method getting invoked on this node if the
ignite has not even fully started on this node ? Which ignite instance is it
using to invoke the record method ?
I have enabled only these events :
Hi,
Going by the thread dump, the event api thread is holding a lock others
need to proceed,
while event storage thread is itself waiting for another condition to
proceed.
The method you are calling determined that you are not accessing ignite
from the same thread
that started it and is
Hello,
Our set up :
Server nodes : 3
Writer application : 1
A event storage spi that writes the cache_put events that have been
generated due to a dbeaver update into a ignite cache.
We restarted one of the servers yesterday during regular business hours and
noticed that the server was not
