Increases interval in cluster test
Fixes issue where batch insertion on existing db would delete indexes

When doing batch insertion on an existing database containing indexes,
those indexes, or rather the configuration for them (as well as the
existence of them from the dbs POV) would be deleted if not used in this
second batch insertion. I.e. any index configuration would be overwritten
with whatever this second batch insertion did.

Problem being that the existing index configuration wasn't read (the call
to indexStore.start()) so when shutting down in the end and writing the
index configuration, any existing would be lost.

Fixes #527
Merge pull request #662 from tinwelint/fix-527

Fixes issue where batch insertion on existing db would delete indexes
Small fixes in cluster creation

Instance now waits far less to create the cluster if it's the only instance configured
Instance now properly waits for half of the cluster to be discovered, instead of half+1
 which was previously and was wrong
Comments and formatting
Renames clusterId management bean field to instanceId, reflecting the removal of URIs as ids

Renames the fields and accessors of ClusterMemberInfo
Removes field from ClusterDatabaseInfo that was used to keep the serverId from HaSettings
Updates tests to match
Fixes logging of errors on push requests from master

Fixes typo in method name
Updates changelogs for 1.9.RC1 - date pending
Adds fair lock for message processing, ensure no messages get held for too long
Adding @Perfect-Pixel. Welcome!
Manage StoreAccess inside GraphStoreFixture.

o Failure to close StoreAccess before deleting underlying files
  was causing test failiures on Windows.
o Also, replaced file-based string logger with StringLogger.SYSTEM
  for non-production cases, since this implementation doesn't need
  to be closed, and it would hard to manage the lifecycle of a
  logger that does need to be closed.
Remove assertion relying on messages.log to detect recovery.