Fixing aggregateJavadoc
questionable test Ignored
First pass at fixing the s3 client TimeoutConnections problem.
Merge pull request #236 from jasobrown/1.1

First pass at fixing the s3 client TimeoutConnections problem. Incorporating @johaho's fix from https://github.com/Netflix/Priam/pull/220. 

reviewed by @sagarl
call s3client.getObjectMetadata() directly, rather than getting sn S3Object first.
Getting the S3Object eagerly opens the TCP connection, which we don't need at all
in the S3FileSystem block.
Merge pull request #237 from jasobrown/1.1

call s3client.getObjectMetadata() directly, rather than getting sn S3Object first

reviewed by @timiblossom
ffs, this again?!?!
Merge pull request #239 from timiblossom/1.1

1.1 - reviewed during checking by Sagar and code by Jason.
lower logging level
Merge pull request #240 from timiblossom/1.1

fix duplicate row keys for nodes on us-west-1 and us-west-2
Make build script happy
First step in supporting commit log archives. Adding properties to configure the CL backup,
and write them out.
Merge pull request #244 from jasobrown/1.1

First step in supporting commit log archives

reviewed by @sloke and @timiblossom
YAGPH (yet another gradle.properties hack)
Merge remote-tracking branch 'build/multi-project' into 1.1
Seed list is now a list of strings in public IP4 format.
This solves these 3 issues in a C* process caused by the bug:

1. Every C* JVM holds 2 connection pools (4 threads total) for each same-region seed node.
   "WRITE-/50.16.3.113" daemon prio=10 tid=0x00007f4404032000 nid=0x1e98 waiting on condition [0x00007f440aca8000]
   "WRITE-/50.16.3.113" daemon prio=10 tid=0x00007f4404096800 nid=0x1e97 waiting on condition [0x00007f440acd5000]
   "WRITE-ec2-50-16-3-113.compute-1.amazonaws.com/10.166.46.179" daemon prio=10 tid=0x00000000019d0800 nid=0x1e95 waiting on condition [0x00007f440ad02000]
   "WRITE-ec2-50-16-3-113.compute-1.amazonaws.com/10.166.46.179" daemon prio=10 tid=0x00000000015be800 nid=0x1e94 waiting on condition [0x00007f4410725000]

   This obviously costs us some CPU and thread resources on every C* node. We only need one connection pool for each remote node.

2. Another problem is that when that seed node goes down, FailureDetector in C* JVM can only help to remove one connection pool (and its threads) associated with that
   down node's Public IP endpoint. The connection pool associated with DNS names would stay. We are wasting 2 more threads on each same-region node when we replace a seed node in Ec2.

3. Avoid some intra-region gossipping between nodes to go through SSL port.  Remember that SSL traffics are only for inter-region connections and all intra-region traffics should go through
   non-SSL port.