a) Updated Voldemort logo (b) Added some more information

push-javadoc.sh

@@ -1,3 +1,10 @@
 #!/bin/bash
 
-rsync -r --progress --cvs-exclude --delete --archive /Users/jkreps/workspace/voldemort/docs/javadoc empathybox@empathybox.com:/home/empathybox/project-voldemort.com/
+if [ $# -lt 1 ]; then
+   echo $0 location-of-javadoc
+   exit 1
+fi
+
+echo Pushing $1...
+
+rsync -r --progress --cvs-exclude --delete --archive $1 snateam@sna-projects.com:/home/empathybox/sna-projects.com/voldemort/javadoc

voldemort/configuration.php

@@ -48,10 +48,17 @@
   </cluster>
 </pre>
 
+<p>
 One thing that is important to understand is that partitions are not static partitions of servers, but rather they are a mechanism for partitioning the key space in such a way that each key is statically mapped to a particular data
-partition. What this means is that a particular cluster may support many stores each with different replication factors&mdash;the replication factor is not hardcoded in the cluster design. This is important, since some data is more important than other data, and the correct trade-off between performance and consistency for one store may be different from another store. The number of data partitions cannot be changed. Online redistribution of data is not yet supported, but this provides the mechanism by which it will work when it is. Partitions will be moved to the new servers (or rebalanced between servers), but the total number of partitions will always remain the same, as will the mapping of key to partition. This means it is important to give a good number of partitions to start with. The script test/integration/generate_partitions.py will generate this part of the config for you.
+partition. What this means is that a particular cluster may support many stores each with different replication factors&mdash;the replication factor is not hardcoded in the cluster design. This is important, since some data is more important than other data, and the correct trade-off between performance and consistency for one store may be different from another store. 
+</p>
+<p>
+Another important point to remember is that the number of data partitions cannot be changed. We do support an online redistribution ( rebalancing ) of partitions. In other words inclusion of new nodes results in moving ownership of partitions, but the total number of partitions will always remain the same, as will the mapping of key to partition. This means it is important to give a good number of partitions to start with. The script <a href="https://github.com/voldemort/voldemort/blob/master/bin/generate_cluster_xml.py">here</a> will generate this part of the config for you.
+</p>
 
+<p>
 Note that the configuration is currently simple files so it is important that the data in cluster.xml and stores.xml be exactly the same on each server, and that the node ids and partitions not be changed, since that can mean that clients will think their data should be on node <i>X</i> when really it was stored on node <i>Y</i>. This limitation will be removed as the configuration is moved into voldemort itself.
+</p>
 
 <h3>Store configuration</h3>
 

voldemort/design.php

@@ -305,7 +305,7 @@
 
 <p>We use versioning and read-repair. This has a the best availability guarantees, and the highest efficiency (only W writes network roundtrips are required for N replicas where W can be configured to be less than N). 2PC typically requires 2N blocking roundtrips. Paxos variations vary quite a bit but are comparable to 2PC.</p>
 
-<p>Many of the specifics are borrowed from the Amazon paper below</p>
+<p>Another approach to reach consistency is by using <i>Hinted Handoff</i>. In this method during writes if we find that the destination nodes are down we store a "hint" of the updated value on one of the alive nodes. Then when these down nodes come back up the "hints" are pushed to them thereby making the data consistent. Many of the specifics are borrowed from the Amazon paper below</p>
 
 <p>Here are some good write-ups on this subject:</p>
 

voldemort/includes/project_info.php

@@ -12,9 +12,12 @@
   $PROJ_KEYWORDS = "Project Voldemort, Voldemort, key-value storage, distributed storage, Amazon Dynamo, persistence, scalability";
 
   /* Favicon image file location and type */
-  $PROJ_FAVICON_PATH = "http://project-voldemort.com/images/vold-logo-small.png";
+  $PROJ_FAVICON_PATH = "images/voldemort_logo_small.png";
   $PROJ_FAVICON_MIME = "image/png";
 
+  /* Project icon in header */
+  $PROJ_ICON_PATH = "images/voldemort_logo.png";
+
   /* Navigation links in the sidebar */
   $PROJ_NAV_LINKS = array(
       "quickstart" => "quickstart.php",
@@ -24,12 +27,10 @@
       "download" => "http://github.com/voldemort/voldemort/downloads",
       "snapshot build" => "http://test.project-voldemort.com:8080/job/voldemort-master",
       "configuration" => "configuration.php",
-      "client javadoc" => "/javadoc/client",
-      "all javadoc" => "/javadoc/all",
+      "javadoc" => "/javadoc/all",
       "developer info" => "developer.php",
       "fun projects" => "http://wiki.github.com/voldemort/voldemort/fun-projects",
       "performance" => "performance.php",
-      "unit tests" => "http://test.project-voldemort.com:8080",
       "bugs" => "http://code.google.com/p/project-voldemort/issues",
       "wiki" => "http://wiki.github.com/voldemort/voldemort");