No description
a188099f91
* I suspect that the issue #15440 happens because of replay of events in wrong order (ShardHomeAllocated received before ShardRegionRegistered) by the hbase journal * This does not fix that issue, but the additional invariant checks and debug statements would perhaps make it easier for us to diagnose such issues * These changes also ensures that the allocation strategy does not return the wrong thing. * It also tightens a possible error if a region is terminated while a rebalance is in progress (cherry picked from commit d07b9db4958236d580b8bfb8f92461969ff88cbc) |
||
|---|---|---|
| akka-actor | ||
| akka-actor-tests | ||
| akka-agent | ||
| akka-bench-jmh/src/main/scala/akka/persistence | ||
| akka-camel | ||
| akka-cluster | ||
| akka-contrib | ||
| akka-docs | ||
| akka-kernel | ||
| akka-multi-node-testkit | ||
| akka-osgi | ||
| akka-persistence | ||
| akka-remote | ||
| akka-remote-tests | ||
| akka-samples | ||
| akka-slf4j | ||
| akka-stream/src | ||
| akka-testkit | ||
| akka-zeromq | ||
| atmos/src/main/resources | ||
| project | ||
| scripts | ||
| src/main/ls | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.textile | ||
h1. Akka We believe that writing correct concurrent, fault-tolerant and scalable applications is too hard. Most of the time it's because we are using the wrong tools and the wrong level of abstraction. Akka is here to change that. Using the Actor Model we raise the abstraction level and provide a better platform to build correct concurrent and scalable applications. For fault-tolerance we adopt the "Let it crash" model which the telecom industry has used with great success to build applications that self-heal and systems that never stop. Actors also provide the abstraction for transparent distribution and the basis for truly scalable and fault-tolerant applications. Akka is Open Source and available under the Apache 2 License. Learn more at "http://akka.io":http://akka.io.