You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by Apache Wiki <wi...@apache.org> on 2010/08/16 08:12:05 UTC
[Hadoop Wiki] Update of "ZooKeeper/GSoCFailureDetector" by AbmarBarros
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "ZooKeeper/GSoCFailureDetector" page has been changed by AbmarBarros.
http://wiki.apache.org/hadoop/ZooKeeper/GSoCFailureDetector?action=diff&rev1=8&rev2=9
--------------------------------------------------
1. --(Refactor client-side code of the client-server monitoring to use the proposed FailureDetector interface)--
1. --(Make the failure detection and its parameters configurable on the client)--
1. --(Refactor server-side code of the client-server monitoring to use the proposed FailureDetector interface)--
- 1. Refactor the code of the server-server monitoring to use the proposed FailureDetector interface
+ 1. --(Refactor the code of the server-server monitoring to use the proposed FailureDetector interface)--
- 1. Make the failure detection and its parameters configurable on the server (to server-server and client-server monitoring)
+ 1. --(Make the failure detection and its parameters configurable on the server (to server-server and client-server monitoring))--
1. Evaluate the QoS metrics with experimentation
- 1. Write Forrest docs
+ 1. --(Write Forrest docs)--
== Related JIRA ==
* [[https://issues.apache.org/jira/browse/ZOOKEEPER-702|ZOOKEEPER-702: GSoC 2010: Failure Detector Model]]
@@ -82, +82 @@
* Created a new FailureDetector, which groups monitoreds by their tick time, similar to what the SessionTracking does.
* Made the server-client failure detector (and its parameters) options of the ZooKeeper configuration file.
- === Currently working on ===
- * Refactoring the code of the server-server monitoring to use the proposed FailureDetector interface
+ ==== 23/Jul/10 ====
+ * Made Learners track client heartbeats and send statistical data of the heartbeat sampling window to the Learner
+ * Analyzed paper about application message used as heartbeat.
+
+ ==== 30/Jul/10 ====
+ * Refactored the code of the Leader-Learner monitoring in order to use failure detector module
+ * Added options in configuration file to configure Leader-Learner monitoring
+ * Fixed bugs in FDs initialization and in some cases of session registering
+ * Fixed bug in server recovery on the client side
+
+ ==== 09/Aug/10 ====
+ * Set up first experiments in Emulab
+ * Instrumented code to report some detection metrics as false suspicion and detection time
+ * Enhanced java documentation, started to write forrest docs
+
+ ==== 14/Aug/10 ====
+ * Kept on changing experimentation scenarios to check the behaviour of the failure detectors
+ * Tuned some initialization parameters of the failure detectors based on some experimentation results
+ * Finished writing forrest documentation
+ * Added a new parameter to phi accrual FD - the minimum window size to begin timeout adaptation.
+ * Added a moderation step to Bertier FD, to comply with second level task described in his paper
+ * Made Chen's alpha parameter configurable, and not a quarter of the timeout
+
+ ==== 16/Aug/10 ====
----
+ == Experimentation ==
+
+ ==== Experimental design ====
+
+ ==== Results and conclusions ====
+
+ ----
== Design decisions ==
==== Should a failure detector instance (FD) run in a separate thread from the application? ====