[infinispan-issues] [JBoss JIRA] Updated: (ISPN-835) State transfer should not force all invocations to be synchronous

[ https://issues.jboss.org/browse/ISPN-835?page=com.atlassian.jira.plugin.s... ] Manik Surtani updated ISPN-835: ------------------------------- Fix Version/s: (was: 4.2.1.Final) Workaround Description: Workaround #1: Disable state transfer - and use a ClusteredCacheLoader to lazily lookup remote state as and when needed. It might require some code changes to make the code efficient, for example: If put() method's return value is not needed, pass Flag.SKIP_CACHE_LOAD so that clustered cache loader is not queried for previous value. Workaround #2: Enable state transfer and REPL_SYNC. Use the Async API (e.g., cache.putAsync(k, v)) to actieve 'fire-and-forget' capabilities. Workaround #3: Enable state transfer and REPL_ASYNC. All RPCs end up becoming sync, but client threads *will not* be held up if you enable a replication queue (which is recommended for async mode anyway). was: Disable state transfer - and use a ClusteredCacheLoader to lazily lookup remote state as and when needed. It might require some code changes to make the code efficient, for example: If put() method's return value is not needed, pass Flag.SKIP_CACHE_LOAD so that clustered cache loader is not queried for previous value. Priority: Major (was: Critical) De-prioritising due to the large number of options as workarounds. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira