[
https://issues.redhat.com/browse/ISPN-10718?page=com.atlassian.jira.plugi...
]
Pedro Zapata Fernandez updated ISPN-10718:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint
#37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint
#35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
Ensure protobuf metadata cache is predictably started when the cache
manager has finished initializing
------------------------------------------------------------------------------------------------------
Key: ISPN-10718
URL:
https://issues.redhat.com/browse/ISPN-10718
Project: Infinispan
Issue Type: Enhancement
Components: Remote Querying
Affects Versions: 10.0.0.CR2
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Priority: Major
Fix For: 10.0.0.Final
Casual code browsing led me to ProtobufMetadataCacheStartedTest where I see we actually
assert that protobuf metadata cache is not started on cache manager start, it is actually
started lazily, when first non-internal cache starts. And the code is written as if this
is a (happy) accident. That's very dangerous. We should start it predictably, when the
cache manager has finished startup.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)