[Bigdata-commit] SF.net SVN: bigdata:[7648] branches/BIGDATA_RELEASE_1_3_0/bigdata-jini/src/ java/com/bigdata/journal/jini/ha/HAJournalServer.java

[<tho...@us...>]

Revision: 7648
          http://bigdata.svn.sourceforge.net/bigdata/?rev=7648&view=rev
Author:   thompsonbry
Date:     2013-12-13 21:05:10 +0000 (Fri, 13 Dec 2013)
Log Message:
-----------
comment on purgeHA()

Modified Paths:
--------------
    branches/BIGDATA_RELEASE_1_3_0/bigdata-jini/src/java/com/bigdata/journal/jini/ha/HAJournalServer.java

Modified: branches/BIGDATA_RELEASE_1_3_0/bigdata-jini/src/java/com/bigdata/journal/jini/ha/HAJournalServer.java
===================================================================
--- branches/BIGDATA_RELEASE_1_3_0/bigdata-jini/src/java/com/bigdata/journal/jini/ha/HAJournalServer.java	2013-12-13 21:01:07 UTC (rev 7647)
+++ branches/BIGDATA_RELEASE_1_3_0/bigdata-jini/src/java/com/bigdata/journal/jini/ha/HAJournalServer.java	2013-12-13 21:05:10 UTC (rev 7648)
@@ -4181,10 +4181,17 @@
                      * Halt operation.
                      * 
                      * Note: This is not an error, but we can not remove
-                     * snapshots or HALogs if this invariant is violated. This
-                     * is because a leader fail could then cause the
-                     * IRestorePolicy to be violated if a service that lacked
-                     * some HALogs was elected as the leader.
+                     * snapshots or HALogs if this invariant is violated.
+                     * 
+                     * Note: We do not permit HALog files to be purged if the
+                     * quorum is not fully met. This is done in order to prevent
+                     * a situation a leader would not have sufficient log files
+                     * on hand to restore the failed service. If this were to
+                     * occur, then the failed service would have to undergo a
+                     * disaster rebuild rather than simply resynchronizing from
+                     * the leader. Hence, HALog files are NOT purged unless the
+                     * quorum is fully met (all services for its replication
+                     * count are joined with the met quorum).
                      */
                     return;
                 }

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.