registering endpoint is moved to authentication request so that we do not register unauthenticated endpoints to client ednpoint manager
Always removed last added partitions from overloaded members.
This should decrease overall no. of migrations during repartitiong.
If a member is detected as dead a repartitioning thread on a master is paused and
its re-activation is scheduled. Other members have time to notice the member
is dead, so they can promote backups and shift partition tables.

When another member is detected as dead while the migration thread is still paused
the original re-activation is now postponed.
MAX_NO_MASTER_CONFIRMATION_SECONDS increased to 500s.

It decrease a chance of data loss when multiple members are running on the same host which dies suddenly.

There are two commonly used mechanisms to detect dead members:
 - heartbeats
 - master confirmation

By increasing the MAX_NO_MASTER_CONFIRMATION_SECONDS we make sure the dead node is always detected by
the heartbeat mechanism. Heartbeats are sent with higher frequency than the master confirmations so there
is a good chance we detect all dead members before re-partitioning process is started.
fix for issue #3047 (throws exception in case of non-comparable)
unit test for issue #3047 (throws exception in case of non-comparable)
unit test for issue #3047 (minor updates on PagingPredicate)
unused code removed
Merge remote-tracking branch 'origin/master' into fix/master/issue-3047
checkstyle fix for issue #3047
unused argument removed
fixing #3162

When a ReplicatedMap proxy is obtained it's pre-populated from another member.
This is an asynchronous process.

If the other member is mutating the replicated map at the same time as the pre-population
is in progress then a same entry can be sent to the new member as two distinct events:
 - once as a part of the initial load
 - once as the result of the map mutation

Both events will have the same state of the vector clock.
I believe this issue caused the occasional test failures as it was evaluated as a conflict
by the vector clock logic. The conflict might result in new update events being generated as
part of the conflict resolution and this eventually confused the test.

The condition can be simulated by introducing delay in ReplicatedMapInitChunkOperation.

The fix is rather easy - if the incoming vector clock has the same state as a local entry then the update
is silently ignored.
Merge pull request #3434 from serkan-ozal/fix/master/issue-3047

Fix/master/issue 3047
Merge pull request #3440 from jerrinot/fix/replicatedMap-ttl/master

fixing #3162
Merge pull request #3433 from jerrinot/fix/dataloss/master

The Dataloss Race Condition fixed
Merge pull request #3425 from sancar/fix/clientEndpointNPE/master

registering endpoint is moved to authentication request so that we do no...
Merge branch 'master' of https://github.com/hazelcast/hazelcast
check if expirable