Fix warnings and clean up javadocs in sal-akka-raft

[controller.git] / opendaylight / md-sal / sal-akka-raft / src / main / java / org / opendaylight / controller / cluster / raft / policy / RaftPolicy.java

diff --git a/opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/policy/RaftPolicy.java b/opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/policy/RaftPolicy.java
index a66caa456a45af5c2be4885f77749f9c0e49f824..c535c2299d5cbbefa1d128f7eb96ab8f725034f7 100644 (file)
--- a/opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/policy/RaftPolicy.java
+++ b/opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/policy/RaftPolicy.java
@@ -13,7 +13,7 @@ package org.opendaylight.controller.cluster.raft.policy;
  * we may want to be able to determine which Raft replica should become the leader - with Raft elections are
  * randomized so it is not possible to specify which replica should be the leader. The ability to specify
  * the leader would be quite useful when testing a raft cluster.
- *
+ * <p/>
  * Similarly we may want to customize when exactly we apply a modification to the state - with Raft a modification
  * is only applied to the state when the modification is replicated to a majority of the replicas. The ability to
  * apply a modification to the state before consensus would be useful in scenarios where you have only 2 nodes
@@ -31,10 +31,10 @@ public interface RaftPolicy {
 
     /**
      * According to Raft consensus on a Raft entry is achieved only after a Leader replicates a log entry to a
-     * majority of it's followers
+     * majority of it's followers.
      *
      * @return true if modification should be applied before consensus, false to apply modification to state
-     * as per Raft
+     *     as per Raft
      */
     boolean applyModificationToStateBeforeConsensus();
 }