anchor.diff:  submitted via any ExecutionService in the cluster.
           
   Since an ExecutionService does not allow for non serializable class instances to be sent across as tasks
  -there are 2 utility classes provided to get around this problem.  For users that are used to using a
  +there are two utility classes provided to get around this problem.  For users that are used to using a
   CompletionService with an Executor there is an equivalent ExecutionCompletionService provided that allows
   for a user to have the same functionality.  It would have been preferred to allow for the same
   ExecutorCompletionService to be used, but due to its implementation using a non serializable object
  
positive.code: <config>
      ...
      <MFC max_credits="2M"
           min_threshold="0.4"/>
      <FRAG2 frag_size="60K"  />
      <COUNTER bypass_bundling="true" timeout="5000"/>
  </config>
          
  ----
  
negative.code: [[CounterService]]
  === Cluster wide atomic counters
  
  Cluster wide counters provide named counters (similar to AtomicLong) which can be changed atomically. Two
  nodes incrementing the same counter with initial value 10 will see 11 and 12 as results, respectively.
          
  To create a named counter, the following steps have to be taken:
  