[infinispan-dev] Changing configuration at runtime
msurtani at redhat.com
Mon Mar 25 14:32:30 EDT 2013
On 22 Mar 2013, at 11:05, Tristan Tarrant <ttarrant at redhat.com> wrote:
> Hi all,
> the current list of configuration parameters which can be tweaked at
> runtime is quite small:
> AsyncStoreConfiguration.flushLockTimeout(long l)
> AsyncStoreConfiguration.shutdownTimeout(long l)
> LockingConfiguration.lockAcquisitionTimeout(long lockAcquisitionTimeout)
> StateTransferConfiguration.timeout(long l)
> StoreAsBinaryConfiguration.enabled(boolean enabled)
> SyncConfiguration.replTimeout(long l)
> TransactionConfiguration.cacheStopTimeout(long l)
> TransactionConfiguration.lockingMode(LockingMode lockingMode)
> TransactionConfiguration.syncCommitPhase(boolean b)
> TransactionConfiguration.syncRollbackPhase(boolean b)
> TransactionConfiguration.useEagerLocking(boolean b)
> We're probably being over-conservative here, and it would be nice to be
> able to tune more parameters, such as async queue size, eviction size,
> default expiration, thread pool configuration and whatever else can be
> done without too much effort.
> Could you all please look at your respective areas of competence and see
> if we can expose any tunable parameters ?
> Obviously these need to be exposed via JMX/RHQ as well.
+1. But this is unlikely to happen by "asking nicely" like this on this list. :-) Your best bet may well be to look at each config option, see which one makes logical sense to tweak at runtime, and run it by anyone who owns that piece of code.
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
manik at jboss.org
Platform Architect, JBoss Data Grid
More information about the infinispan-dev