From c28a26f3eb29dec9952cc460e18b409a7154f929 Mon Sep 17 00:00:00 2001
From: Don Naro <dnaro@redhat.com>
Date: Mon, 21 Sep 2020 12:12:34 +0100
Subject: [PATCH] ISPN-12344 cannot preload shared remote stores

---
 .../resources/schema/infinispan-config-12.0.xsd  |  2 +-
 .../asciidoc/topics/ref_cache_store_remote.adoc  | 16 +++++++++++-----
 2 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/core/src/main/resources/schema/infinispan-config-12.0.xsd b/core/src/main/resources/schema/infinispan-config-12.0.xsd
index c03f4977deb7..f8da77a2c0fa 100644
--- a/core/src/main/resources/schema/infinispan-config-12.0.xsd
+++ b/core/src/main/resources/schema/infinispan-config-12.0.xsd
@@ -1841,7 +1841,7 @@
     </xs:attribute>
     <xs:attribute name="preload" type="xs:boolean" default="${AbstractStore.preload}">
       <xs:annotation>
-        <xs:documentation>If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.</xs:documentation>
+        <xs:documentation>If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process. Likewise in some cases you cannot pre-load data in caches stores, such as when using shared remote stores.</xs:documentation>
       </xs:annotation>
     </xs:attribute>
     <xs:attribute name="fetch-state" type="xs:boolean" default="${AbstractStore.fetchPersistentState}">
diff --git a/documentation/src/main/asciidoc/topics/ref_cache_store_remote.adoc b/documentation/src/main/asciidoc/topics/ref_cache_store_remote.adoc
index 60fc714c780b..1d161a1288ba 100644
--- a/documentation/src/main/asciidoc/topics/ref_cache_store_remote.adoc
+++ b/documentation/src/main/asciidoc/topics/ref_cache_store_remote.adoc
@@ -1,12 +1,18 @@
 [id='remote_cache_store']
 = Remote Cache Stores
-Remote cache stores, `RemoteStore`, use a remote {brandname} cluster as storage.
+Remote cache stores, `RemoteStore`, use the Hot Rod protocol to store data on
+{brandname} clusters.
 
-`RemoteStore` uses the Hot Rod protocol to communicate with remote {brandname}
-clusters.
+The following is an example `RemoteStore` configuration that stores data in a
+cache named "mycache" on two {brandname} Server instances, named "one" and
+"two":
 
-In the following configuration examples, `RemoteStore` uses the remote cache
-named "mycache" on {brandname} servers "one" and "two":
+[NOTE]
+====
+If you configure remote cache stores as shared you cannot preload data. In
+other words if `shared="true"` in your configuration then you must set 
+`preload="false"`.
+====
 
 .Declarative configuration