anchor.diff:  % reply. A long interval also increases the likelihood that the server
   % crashes before the commit has finished successfully, making requests
   % more unreliable.
  --define(DELAYED_FLUSH_INTERVAL, 1 * ?SECOND).
  +-define(DELAYED_FLUSH_INTERVAL, (1 * ?SECOND)).
   
   % How long to wait between garbage collection runs.
   -define(GC_INTERVAL, ?DAY).
   
   % Max duration for a GC run.  This should be smaller than
   % min(ORPHANED_{BLOB,TAG}_EXPIRES).
  --define(GC_MAX_DURATION, 3 * ?DAY).
  +-define(GC_MAX_DURATION, (3 * ?DAY)).
   
   % How long to wait after startup for cluster to stabilize before
   % starting the first GC run.
  --define(GC_DEFAULT_INITIAL_WAIT, 5 * ?MINUTE).
  +-define(GC_DEFAULT_INITIAL_WAIT, (5 * ?MINUTE)).
   
   % Maximum number of times we try to bring up a node that failed during
   % GC before we abort GC.
  
positive.code: % How long to wait before timing out a tag retrieval.  This should be
  % large enough to read a large tag object off the disk and send it
  % over the network.
  -define(GET_TAG_TIMEOUT, 5 * ?MINUTE).
  
negative.code: % The longest potential interval between messages in the GC protocol;
  % used to ensure GC makes forward progress.  This can be set to the
  % estimated time to traverse all the volumes on a DDFS node.
  -define(GC_PROGRESS_INTERVAL, (30 * ?MINUTE)).
  
  % Number of extra replicas (i.e. lost replicas recovered during GC) to
  % allow before deleting extra replicas.
  