Bug 1168043

In Red Hat JBoss Data Grid, for a cache store where <parameter>sharing</parameter> is set to <literal>false</literal>, the <parameter>fetchInMemory</parameter> and <parameter>fetchPersistence</parameter> parameters must also be set to <literal>true</literal> or different nodes may contain different copies of the same data. For a cache store where the <parameter>shared</parameter> parameter is set to <literal>true</literal>, set <parameter>fetchPersistence</parameter> must be set to <literal>false</literal> because the persistence is shared and enabling it results in unnecessary state transfers. However, the <parameter>fetchInMemory</parameter> parameter can be set to either <literal>true</literal> or <literal>false</literal>. Setting this to <literal>true</literal> loads the in-memory state via the network and resulted in a faster start up. Setting the value to <literal>false</literal> loads the data from persistence without transferring the data remotely from other nodes. This is a known issue in JBoss Data Grid 6.4 and the only workaround for this issue is to follow the stated guidelines above and to ensure that each node in the cluster uses the same configuration to prevent unexpected results based on the start up order.