Arthur Wang created IGNITE-17747:
------------------------------------
Summary: When the Ignite server is restarted, the client cannot
destroy the instantiated queue and reinstantiate it, except to restart the
client application
Key: IGNITE-17747
URL: https://issues.apache.org/jira/browse/IGNITE-17747
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Arthur Wang
Attachments: log.png
In the case of Ignite single-node deployment, when the Ignite server is
restarted, the client cannot destroy the instantiated queue and reinstantiate
it, except to restart the client application. This means that Ignite queue does
not take advantage of getOrCreate's recovery mechanism like the k-v caches.Is
there any good practice to restore the usability of Queue without restarting
the client?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)