BUG 2185 : Make the Custom Raft Policy externally configurable

[controller.git] / opendaylight / md-sal / sal-clustering-config / src / main / resources / initial / datastore.cfg

diff --git a/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/datastore.cfg b/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/datastore.cfg
index cfbf9450aa2b77661f21bd00904a995b48c9c3d7..13ccf93f5ee2311494e159ba68752129b70c94bb 100644 (file)
--- a/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/datastore.cfg
+++ b/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/datastore.cfg
@@ -51,7 +51,7 @@ operational.persistent=false
 # The number of transaction modification operations (put, merge, delete) to batch before sending to the 
 # shard transaction actor. Batching improves performance as less modifications messages are sent to the 
 # actor and thus lessens the chance that the transaction actor's mailbox queue could get full.
-#shard-batched-modification-count=100
+#shard-batched-modification-count=1000
 
 # The maximum amount of time for akka operations (remote or local) to complete before failing.
 #operation-timeout-in-seconds=5
@@ -73,3 +73,11 @@ operational.persistent=false
 # The maximum queue size for each shard's data store executor.
 #max-shard-data-store-executor-queue-size=5000
 
+# A fully qualified java class name. The class should implement
+# org.opendaylight.controller.cluster.raft.policy.RaftPolicy. This java class should be
+# accessible to the distributed data store OSGi module so that it can be dynamically loaded via
+# reflection. For now let's assume that these classes to customize raft behaviors should be
+# present in the distributed data store module itself. If this property is set to a class which
+# cannot be found then the default raft policy will be applied
+#custom-raft-policy-implementation=
+