Merge pull request #28595 from akka/wip-doc-chg-transport-patriknw
note about rolling update when changing transport
This commit is contained in:
commit
ece9e7d92b
2 changed files with 9 additions and 4 deletions
|
|
@ -154,6 +154,10 @@ which has a completely different protocol, a rolling update is not supported.
|
||||||
For more details on this migration
|
For more details on this migration
|
||||||
see @ref:[the migration guide](../project/migration-guide-2.5.x-2.6.x.md#migrating-from-classic-remoting-to-artery).
|
see @ref:[the migration guide](../project/migration-guide-2.5.x-2.6.x.md#migrating-from-classic-remoting-to-artery).
|
||||||
|
|
||||||
|
### Changing remoting transport
|
||||||
|
|
||||||
|
Rolling update is not supported when @ref:[changing the remoting transport](../remoting-artery.md#selecting-a-transport).
|
||||||
|
|
||||||
### Migrating from Classic Sharding to Typed Sharding
|
### Migrating from Classic Sharding to Typed Sharding
|
||||||
|
|
||||||
If you have been using classic sharding it is possible to do a rolling upgrade to typed sharding using a 3 step procedure.
|
If you have been using classic sharding it is possible to do a rolling upgrade to typed sharding using a 3 step procedure.
|
||||||
|
|
|
||||||
|
|
@ -133,12 +133,13 @@ It has very good performance (high throughput and low latency) but latency at hi
|
||||||
might not be as good as the Aeron transport. It has less operational complexity than the
|
might not be as good as the Aeron transport. It has less operational complexity than the
|
||||||
Aeron transport and less risk of trouble in container environments.
|
Aeron transport and less risk of trouble in container environments.
|
||||||
|
|
||||||
@@@ note
|
|
||||||
|
|
||||||
Aeron requires 64bit JVM to work reliably and is only officially supported on Linux, Mac and Windows.
|
Aeron requires 64bit JVM to work reliably and is only officially supported on Linux, Mac and Windows.
|
||||||
It may work on other Unixes e.g. Solaris but insufficient testing has taken place for it to be
|
It may work on other Unixes e.g. Solaris but insufficient testing has taken place for it to be
|
||||||
officially supported. If you're on a Big Endian processor, such as Sparc, it is recommended to use
|
officially supported. If you're on a Big Endian processor, such as Sparc, it is recommended to use TCP.
|
||||||
TCP.
|
|
||||||
|
@@@ note
|
||||||
|
|
||||||
|
@ref:[Rolling update](additional/rolling-updates.md) is not supported when changing from one transport to another.
|
||||||
|
|
||||||
@@@
|
@@@
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue