* Failure detection heartbeating was not performed to joining
nodes, since it was expected that they will become Up first.
* If a joining node is downed before it is changed to Up failure
detection will not be performed for that node. That resulted in
the downed node will not be removed from membership, since the
unreachability signal is used as confirmation that the node is
actually stopped before removing it.
* The old implementation would cap the pool size (both corePoolSize
and maximumPoolSize) to max-pool-size, which is very confusing
becuase maximumPoolSize is only used when the task queue is bounded.
* That resulted in configuring core-pool-size-min and core-pool-size-max
was not enough, because it could be capped by the default max-pool-size.
* The new behavior is simply that maximumPoolSize is adjusted to not be
less than corePoolSize, but otherwise the config properties match the
underlying ThreadPoolExecutor implementation.
* Added a convenience fixed-pool-size property.
Publish appropriate events to the current ActorSystem event stream upon remote ActorSystem shutdown or when current ActorSystem is quarantined by the remote ActorSystem.
* DeathPactException could occur if the ReliableDeliverySupervisor
was gated but not yet received Terminated and got an Ungate message
from the EndpointManager and thereby entered idle state, followed by
receiving the Terminated message, which is not handled in idle
For all docs:
* remove consecutive duplicate words
* Improve use of commata
* Improve use of articles
* Improve consistent use of singular/plural
* Simplify run-on sentences
Review iterations:
* Integrate @rkuhn review points
- bring back the comma for the interjection
- ‘to not’ is not inverted if the infinitive form still follows
- Elegantly connect a run on sentence with a semicolon
- Correct semantic error
- Strictly monotonically preserve math expressions
- Use correct english futures
* Cross sync changes to files in scala, java & java-lambda documentation files using git diff -u | patch
* JournalProxy works on the journal and snapshot store
message protocol level and is therefore much simpler
than the previous AsyncWriteProxy approach
* JournalProxy will work out of the box with any journal,
I have tried with Cassandra
* should in the end phase out AsyncWriteProxy and
SharedLeveldbJournal, we need deprecation phase
* rewrote the InmemJournal to remove the dependency to
AsyncWriteProxy, which I can't see why it is needed
for the InmemJournal
