.hibernate-search-infinispan.4.3.0.Final.source-code.default-hibernatesearch-infinispan.xml Maven / Gradle / Ivy
<?xml version="1.0" encoding="UTF-8"?> <!-- * Hibernate, Relational Persistence for Idiomatic Java * * Copyright (c) 2012, Red Hat, Inc. and/or its affiliates or third-party contributors as * indicated by the @author tags or express copyright attribution * statements applied by the authors. All third-party contributions are * distributed under license by Red Hat, Inc. * * This copyrighted material is made available to anyone wishing to use, modify, * copy, or redistribute it subject to the terms and conditions of the GNU * Lesser General Public License, as published by the Free Software Foundation. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY * or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License * for more details. * * You should have received a copy of the GNU Lesser General Public License * along with this distribution; if not, write to: * Free Software Foundation, Inc. * 51 Franklin Street, Fifth Floor * Boston, MA 02110-1301 USA --> <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" xmlns="urn:infinispan:config:5.2"> <!-- *************************** --> <!-- System-wide global settings --> <!-- *************************** --> <global> <!-- Duplicate domains are allowed so that multiple deployments with default configuration of Hibernate Search applications work - if possible it would be better to use JNDI to share the CacheManager across applications --> <globalJmxStatistics enabled="false" cacheManagerName="HibernateSearch" allowDuplicateDomains="true" /> <!-- If the transport is omitted, there is no way to create distributed or clustered caches. There is no added cost to defining a transport but not creating a cache that uses one, since the transport is created and initialized lazily. --> <transport clusterName="HibernateSearch-Infinispan-cluster" > <!-- Note that the JGroups transport uses sensible defaults if no configuration property is defined. See the JGroupsTransport javadocs for more flags --> </transport> <!-- Note that the JGroups transport uses sensible defaults if no configuration property is defined. See the Infinispan wiki for more JGroups settings: http://community.jboss.org/wiki/ClusteredConfigurationQuickStart --> <!-- Used to register JVM shutdown hooks. hookBehavior: DEFAULT, REGISTER, DONT_REGISTER. Hibernate Search takes care to stop the CacheManager so registering is not needed --> <shutdown hookBehavior="DONT_REGISTER" /> </global> <!-- *************************** --> <!-- Default "template" settings --> <!-- *************************** --> <default> <locking lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false" /> <invocationBatching enabled="false" /> <!-- This element specifies that the cache is clustered. modes supported: distribution (d), replication (r) or invalidation (i). Don't use invalidation to store Lucene indexes (as with Hibernate Search DirectoryProvider). Replication is recommended for best performance of Lucene indexes, but make sure you have enough memory to store the index in your heap. Also distribution scales much better than replication on high number of nodes in the cluster. --> <clustering mode="replication"> <!-- Prefer loading all data at startup than later --> <stateTransfer timeout="480000" fetchInMemoryState="true" /> <!-- Network calls are synchronous by default --> <sync replTimeout="20000" /> </clustering> <jmxStatistics enabled="true" /> <eviction maxEntries="-1" strategy="NONE" /> <expiration maxIdle="-1" /> </default> <!-- ******************************************************************************* --> <!-- Individually configured "named" caches. --> <!-- --> <!-- While default configuration happens to be fine with similar settings across the --> <!-- three caches, they should generally be different in a production environment. --> <!-- --> <!-- Current settings could easily lead to OutOfMemory exception as a CacheStore --> <!-- should be enabled, and maybe distribution is desired. --> <!-- ******************************************************************************* --> <!-- *************************************** --> <!-- Cache to store Lucene's file metadata --> <!-- *************************************** --> <namedCache name="LuceneIndexesMetadata"> <clustering mode="replication"> <stateTransfer fetchInMemoryState="true" /> <sync replTimeout="25000" /> </clustering> </namedCache> <!-- **************************** --> <!-- Cache to store Lucene data --> <!-- **************************** --> <namedCache name="LuceneIndexesData"> <clustering mode="replication"> <stateTransfer fetchInMemoryState="true" /> <sync replTimeout="25000" /> </clustering> </namedCache> <!-- ***************************** --> <!-- Cache to store Lucene locks --> <!-- ***************************** --> <namedCache name="LuceneIndexesLocking"> <clustering mode="replication"> <stateTransfer fetchInMemoryState="true" /> <sync replTimeout="25000" /> </clustering> </namedCache> </infinispan>
© 2015 - 2025 Weber Informatics LLC | Privacy Policy