[DRBD-cvs] svn commit by lars - r2577 - trunk - get the roadmap slightly closer to the actual implement

[drbd-cvs at lists.linbit.com]

Author: lars
Date: 2006-10-31 16:48:32 +0100 (Tue, 31 Oct 2006)
New Revision: 2577

Modified:
   trunk/ROADMAP
Log:
get the roadmap slightly closer to the actual implementation

Modified: trunk/ROADMAP
===================================================================
--- trunk/ROADMAP	2006-10-31 15:46:24 UTC (rev 2576)
+++ trunk/ROADMAP	2006-10-31 15:48:32 UTC (rev 2577)
@@ -239,15 +239,9 @@
 
  Read after write dependencies
 
-  The shared state is available to clusters using protocol C
-  and B. It is not usable with protocol A.
+  The shared mode is available to clusters using protocol C.
+  It is not usable with protocol A or B.
 
-  To support the shared state with protocol B, upon a read
-  request the node has to check if a new version of the block
-  is in the progress of getting written. (== search for it on
-  active_ee and done_ee. [ Since it is on active_ee before the 
-  RecvAck is sent. ] )
-  
  Global write order
 
   [ Description of GFS-mode-arbitration2.pdf ]
@@ -269,6 +263,10 @@
     There are many cases in which such concurrent writes would
     lead to different data on our two copies of the block. 
 
+  *** FIXME ***
+  description of algorithm here is out of date,
+  we handle things slightly differently now in the code.
+
   2. Concurrent writes, network latency is lower than disk latency
     As we can see on the left side in figure two this could lead
     to N1 has the blue version (=data from FS on N2) while N2
@@ -544,6 +542,9 @@
 	    --humand and --timeout-expired are removed.
 	    Everything seems to work so far.
 
+  Known issues: we have to define behaviour for two-primaries case,
+  and for connection loss when Primary with local disk != UpToDate.
+
 17 Something like
 
    drbdx: WARNING disk sizes more than 10% different