hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject hbase git commit: HBASE-16256 Purpose of EnvironmentEdge, EnvironmentEdgeManager (Sai Teja Ranuva)
Date Fri, 29 Jul 2016 23:36:21 GMT
Repository: hbase
Updated Branches:
  refs/heads/branch-1.2 88c991e4a -> 4541d7059


HBASE-16256 Purpose of EnvironmentEdge, EnvironmentEdgeManager (Sai Teja Ranuva)


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/4541d705
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/4541d705
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/4541d705

Branch: refs/heads/branch-1.2
Commit: 4541d70598b0662da4f5a90822cf6b71f6ac48b6
Parents: 88c991e
Author: stack <stack@apache.org>
Authored: Fri Jul 29 16:34:22 2016 -0700
Committer: stack <stack@apache.org>
Committed: Fri Jul 29 16:36:15 2016 -0700

----------------------------------------------------------------------
 .../hbase/util/EnvironmentEdgeManager.java      | 34 ++++++++++++++++++++
 1 file changed, 34 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/4541d705/hbase-common/src/main/java/org/apache/hadoop/hbase/util/EnvironmentEdgeManager.java
----------------------------------------------------------------------
diff --git a/hbase-common/src/main/java/org/apache/hadoop/hbase/util/EnvironmentEdgeManager.java
b/hbase-common/src/main/java/org/apache/hadoop/hbase/util/EnvironmentEdgeManager.java
index b9c1bf2..3674156 100644
--- a/hbase-common/src/main/java/org/apache/hadoop/hbase/util/EnvironmentEdgeManager.java
+++ b/hbase-common/src/main/java/org/apache/hadoop/hbase/util/EnvironmentEdgeManager.java
@@ -24,6 +24,40 @@ import org.apache.hadoop.hbase.classification.InterfaceAudience;
  * Manages a singleton instance of the environment edge. This class shall
  * implement static versions of the interface {@link EnvironmentEdge}, then
  * defer to the delegate on invocation.
+ * <br>
+ * <b>Original Motivation:</b>
+ * The main purpose of the Environment Edge Manager was to have better control
+ * over the tests so that they behave the same when run in any system.
+ * (Refer: <a href="https://issues.apache.org/jira/browse/HBASE-2578">HBASE-2578</a>
- The issue
+ * which added the {@link org.apache.hadoop.hbase.util.EnvironmentEdgeManager}).
+ * The idea is to have a central place where time can be assigned in HBase. That makes
+ * it easier to inject different implementations of time. The default environment edge is
the Java
+ * Current Time in millis. The environment edge manager class is designed to be able
+ * to plug in a new implementation of time by simply injecting an implementation
+ * of {@link org.apache.hadoop.hbase.util.EnvironmentEdge} interface to
+ * {@link org.apache.hadoop.hbase.util.EnvironmentEdgeManager}
+<p>
+ <b>Problems with Environment Edge:</b><br>
+ 1. One of the major problems is the side effects of injecting an Environment Edge into
+    Environment Edge Manager.<br>
+    For example, A test could inject an edge to fast forward time in order to avoid thread
+    sleep to save time, but it could trigger a premature waking up of another thread waiting
+    on a condition dependent on time lapse, which could potentially affect the normal
+    working of the system leading to failure of tests.<br>
+ 2. Every test should ensure it is setting the Environment Edge it needs for the test to
+    perform in an expected way. Because another test which might have run before the current
test
+    could have injected its own custom Environment Edge which may not be applicable to this
+    test. This is still solvable but the problem is that the tests can run in parallel
+    leading to different combinations of environment edges being injected causing unexpected
+    results.<br>
+ 3. Another important issue with respect to injecting time through Environment Edge is that
+    the milliseconds unit of time is ingrained throughout the codebase in the form of hardcoded
+    sleep time or timeouts that any change of time unit or making it fast or slow can potentially
+    trigger unexpected failures due to timeout or unintended flow of execution.<br>
+</p>
+ Because of the above issues, only {@link org.apache.hadoop.hbase.util.DefaultEnvironmentEdge}
+ is being used, whose implementation of time returns the {@link System#currentTimeMillis()}.
It
+ is advised not to inject any other {@link org.apache.hadoop.hbase.util.EnvironmentEdge}.
  */
 @InterfaceAudience.Private
 public class EnvironmentEdgeManager {


Mime
View raw message