[
https://issues.jboss.org/browse/ISPN-9282?page=com.atlassian.jira.plugin....
]
Gustavo Fernandes updated ISPN-9282:
------------------------------------
Description:
The server does not respect the stop order of the caches dictated by cache manager and
tries to stop all caches in random order.
When a cache is indexed and uses the "near-real-time" index manager, it relies
on the indexing caches being available during shutdown of the data cache so that it can
properly flush the index to persistence storage, and this fails due to one or more index
caches being unavailable.
was:
The server does not respect the stop order of the caches dictated by cache manager and
tries to stop all caches in random order.
When a cache is indexed and uses the "near-real-time", it relied on the indexing
caches being available so that it can properly flush the index to persistence storage, and
this fails due to one or more index caches being gone.
Near-Real-Time indexes lost when server is stopped
--------------------------------------------------
Key: ISPN-9282
URL:
https://issues.jboss.org/browse/ISPN-9282
Project: Infinispan
Issue Type: Bug
Components: Indexing, Server
Reporter: Gustavo Fernandes
The server does not respect the stop order of the caches dictated by cache manager and
tries to stop all caches in random order.
When a cache is indexed and uses the "near-real-time" index manager, it relies
on the indexing caches being available during shutdown of the data cache so that it can
properly flush the index to persistence storage, and this fails due to one or more index
caches being unavailable.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)