Bug 1282497 - Creation of internal caches related to Indexing should use a good default or autoconfiguration
Summary: Creation of internal caches related to Indexing should use a good default or ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan, Server
Version: 6.5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.6.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-16 15:33 UTC by wfink
Modified: 2025-02-10 03:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:48:30 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-7350 0 Major Resolved InfinispanIndexProvider should provide sensible defaults for index caches 2019-10-08 07:44:22 UTC

Description wfink 2015-11-16 15:33:28 UTC
Description of problem:
If a distributed cache enable indexing with the infinispan as provider, without any additional configuration, the necessary cahes are created with default settings.
This end up with local caches and the index is not shared, so a Query on different nodes will show different (wrong) results.

Actual results:
LuceneIndexesMetadata, LuceneIndexesLocking and LuceneIndexesData caches are created in local mode.

Expected results:
All three cahces should be created in a mode related to the cache and index.provider. Which can be local (local and REPL caches) or shared(REPL/DIST) if the cahce is distributed

Comment 9 Red Hat Bugzilla 2025-02-10 03:48:30 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.